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

[jgl...@cloudbees.com (JIRA)]

Jesse Glick created JENKINS-22631 OutOfOrderBuildMonitor fails to correct builds with duplicate number Issue Type: Bug Assignee: Jesse Glick Components: core Created: 15/Apr/14 4:33 PM Description: 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. Project: Jenkins Labels: diagnostics Priority: Major Reporter: Jesse Glick

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.