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

[Xavier Coulon (JIRA)]

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

Xavier Coulon commented on JBIDE-15472:
---------------------------------------

Here are my 2c:

- would a new issue be opened for each build failure ? I'd be concerned with the number of issues that would be created, then..
- there's a Jenkins widget that can be installed on user's personal JIRA dashboard. It links to the public jenkins instance (not the private one, sadly)
- would the script that generates the issue also closes it if the build becomes stable again ? because otherwise, it would become a real mess to manage in JIRA
- it could be usefull if it was triggered after a certain amount of build failures or a certain "quite" time after the last build failure. Like a reminder. Said another way, it should be possible to "stay under the radar" of this script. We sometimes get build failures (nexus/network/disk issues) that don't repeat if we kick another job just after. So there should not be an issue creation for that.

IMO, the issue description should just provide links to the tests with failure/errors so that we can quickly get to the problem. No real need to put the whole stacktrace in the description.

Those were my 2c ;-)    
                
> 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