|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I am still on the fence as to whether this is really needed, if JENKINS-26834 were implemented (which I hope to do soonish). The proposed use case in the PR could be satisfied just by recording the JUnit results, then checking the build status and deciding whether to proceed based on that. A special step like this would be needed only if you wanted a finer-grained decision, such as checking the results of a specific test case (which the current PR does not offer), or proceeding only if fewer than ten tests failed, etc.