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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-15472:
---------------------------------------------

If this is just for running when needed then it is less of an issue but would be nice to avoid cluttering more jiras in for same test issues.

My "watermark" idea was so instead of keep adding new jiras the script could check if there are still unresolved issues for the same test scenario, and instead of adding new jira just add comment to the jira about it continue to fail/be an issue.

Something like, when creating an issue add unique part to the jira title, i.e. "job/jbosstools-server_41 repeated test failures" where "job/jbosstools-server_41" identifies the job and "job/" makes it fairly unlikely a human would enter similar issue.

Then when running this script you simply search for unresolved issues "job/jbosstools-server_41" in the title and if there is one add a comment instead of keep adding same jira content.


                
> 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