|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-15155) Show total number of... [email protected] (JIRA)
- [JIRA] (JENKINS-15155) Show total numb... [email protected] (JIRA)
- [JIRA] (JENKINS-15155) Show total numb... [email protected] (JIRA)
- [JIRA] (JENKINS-15155) Show total numb... [email protected] (JIRA)
- [JIRA] (JENKINS-15155) Show total numb... [email protected] (JIRA)
- [JIRA] (JENKINS-15155) Show total numb... [email protected] (JIRA)
- [JIRA] (JENKINS-15155) Show total numb... [email protected] (JIRA)
- [JIRA] (JENKINS-15155) Show total numb... [email protected] (JIRA)

Adding a check for the number of test on my side would only fix the problem for me, whereas fixing the issues in Jenkins helps others, too. So I prefer the latter.
I usually update Jenkins regularly, so I would be OK with a core change as I would get that change soon anyway. I'm not sure how many users are stuck on an older Jenkins version but are able to update the plugin, thus I'm also not sure whether changing the code in the plugin really helps those users.
Regarding the format, I'd prefer a slightly more human readable string like "3 of 10 failed (+2)". I'd also say "0 of 10 failed (±0)" instead of "no failures" if there were no failures.