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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-15472:
----------------------------------------

I'm not sure it's necessary to have this automated with a script.
Just planning weekly 30 minutes from someone in the team to review Jenkins builds and send a report or open a bug to components in error would be enough.
[~maxandersen] IMO, it's just a matter of assigning this task to someone, and creating a Zimbra event to make sure it's done regularly.
                
> 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