[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=12803125#comment-12803125 ] 

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

Right now it's just a python script, which must be run as a given jboss.org and RH Kerberos user - two different logins. I don't see a way to easily embed those login credentials into a tool w/o them being in plaintext, and I don't want to share my login with the world. 

So, it's simply a way to fetch the information from a Jenkins test failure report, dump it as XML into a JIRA, and assign it to the correct component for them to see, pick up, and work on.

As to the frequency of their creation, it's still ad hoc for now. I (or anyone, really) can look at these views and from time to time look at the red balls to see who's been misbehaving:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/

Then I (or anyone) can run the python script to generate a JIRA.

Regarding watermarking, I've already started using a label, "testfailure", so that a query like this is possible:

https://issues.jboss.org/issues/?jql=project%20in%20%28JBIDE%29%20and%20affectedVersion%20in%20%28%224.1.1.Alpha1%22%29%20AND%20labels%20%3D%20testfailure

The point of this is NOT to produce extra crap that devs have to manage. It's to provide more visibility, traceability, and auditing of when test failures go unnoticed. And to reduce the time I spend on nagging people from minutes to seconds, when such a nag is required.

                
> 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