[jbosstools-issues] [JBoss JIRA] (JBIDE-15472) Improve visibility for developers when test failures persist for multiple builds (Jenkins emails are ignored)

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803149#comment-12803149 ] 

Nick Boldt commented on JBIDE-15472:
------------------------------------

I've improved the script so that before creating a new JIRA, the user is asked:

{quote}
Search for Test Failure JIRAs in JBIDE 4.1.1.Alpha1 for server component:

 * https://issues-stg.jboss.org/issues/?jql=labels+IN+%28%22testfailure%22%29+AND+project+IN+%28JBIDE%29+AND+affectedVersion+IN+%28%224.1.1.Alpha1%22%29+AND+component+IN+%28%22server%22%29

Found 1 existing JIRAs:

 * https://issues-stg.jboss.org/browse/JBIDE-15428: 8 Test Failure(s) in JBIDE 4.1.1.Alpha1 for server component

Create new JIRA? [Y/n] 
{quote}

Also moved the above search link higher up in the JIRA description so it's easier to find, and added the # of test failures to the JIRA title - "8 Test Failure(s) in JBIDE 4.1.1.Alpha1 for server component" instead of "Test Failure(s) in JBIDE 4.1.1.Alpha1 [server]".



                
> Improve visibility for developers when test failures persist for multiple builds (Jenkins emails are ignored)
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-15472
>                 URL: https://issues.jboss.org/browse/JBIDE-15472
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: build
>            Reporter: Nick Boldt
>
> First iteration: https://issues.jboss.org/browse/JBIDE-15470, as generated by this: https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTestFailureJIRA.py
> [~maxandersen] said:
> {quote} i would put the details in attachment i think. its a bit overloaded otherwise I think,
>  btw. is this something you will run when you find a failed buid or did you say you would detect when hit a certain amont of fail you generate it ?
> if auto generated shuold take care to not keep opening new jiras again andagain ;)
> maybe add a "watermark" to detect stil open test failure jiras
> {quote}
> Idea here is to run this tool as needed when I notice that builds which are supposed to be frozen and stable are showing test failures persisting for multiple builds. Could also run against master jobs, but less critical.
> Not sure what you mean by a watermark, or how that would be implemented. Please elaborate.
> As this is purely a workflow optimization, it does NOT affect docs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira