[JIRA] [core] (JENKINS-22631) OutOfOrderBuildMonitor fails to correct builds with duplicate number

[dogf...@java.net (JIRA)]

dogfood commented on JENKINS-22631 OutOfOrderBuildMonitor fails to correct builds with duplicate number Integrated in jenkins_main_trunk #3312 [FIXED JENKINS-22631] Do not just warn about multiple builds with the same number; note this in the official problem list, and offer to fix it. (Revision deb90a493c5341274fec11e653b44d7ad8b33586) Result = UNSTABLE Jesse Glick : deb90a493c5341274fec11e653b44d7ad8b33586 Files : test/src/test/resources/jenkins/diagnostics/ooom/OutOfOrderBuildDetectorTest/buildNumberClash.zip test/src/test/groovy/jenkins/diagnostics/ooom/OutOfOrderBuildDetectorTest.groovy core/src/main/java/jenkins/diagnostics/ooom/Problem.java core/src/main/java/jenkins/diagnostics/ooom/BuildPtr.java changelog.html

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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.