-
Bug
-
Resolution: Fixed
-
Major
A user reported a case where on occasion two distinct build records for a job shared the same build number. (The symlink pointed to the later one, and Jenkins loaded the later one, but this apparently caused problems for the Copy Artifact plugin.) The OOOBM did run, printing to the system log for example
... jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Multiple builds have the same number: /.../jobs/.../builds/2014-01-23_09-12-34:#18 vs /.../jobs/.../builds/2014-01-23_15-34-56:#18
yet the older build record (/.../jobs/.../builds/2014-01-23_09-12-34/ in the above example) remained on disk, and no warning was displayed in the OOOBM log.
Code changed in jenkins
User: Jesse Glick
Path:
changelog.html
core/src/main/java/jenkins/diagnostics/ooom/BuildPtr.java
core/src/main/java/jenkins/diagnostics/ooom/Problem.java
test/src/test/groovy/jenkins/diagnostics/ooom/OutOfOrderBuildDetectorTest.groovy
test/src/test/resources/jenkins/diagnostics/ooom/OutOfOrderBuildDetectorTest/buildNumberClash.zip
http://jenkins-ci.org/commit/jenkins/deb90a493c5341274fec11e653b44d7ad8b33586
Log:
[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.
Compare: https://github.com/jenkinsci/jenkins/compare/b36176736f80...deb90a493c53