Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-22631

OutOfOrderBuildMonitor fails to correct builds with duplicate number

      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.

          [JENKINS-22631] OutOfOrderBuildMonitor fails to correct builds with duplicate number

          Jesse Glick created issue -
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          Daniel Beck made changes -
          Labels Original: diagnostics New: diagnostics lts-candidate
          Oliver Gondža made changes -
          Labels Original: diagnostics lts-candidate New: 1.554.2-fixed diagnostics
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 154741 ] New: JNJira + In-Review [ 195011 ]

            jglick Jesse Glick
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: