]
Nick Boldt closed JBIDE-15472.
------------------------------
Assignee: Nick Boldt
Fix Version/s: 4.2.0.Beta2
(was: 4.2.x)
Resolution: Done
Closing. If I come up with a better way to automatically nag people about test failures
that have gone on for more than a couple builds, I'll open a new JIRA and use
something like
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
Assignee: Nick Boldt
Fix For: 4.2.0.Beta2
First iteration:
https://issues.jboss.org/browse/JBIDE-15470, as generated by this:
https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTestF...
[~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.