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

Duplicate build numbers in the Build History

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: build-pipeline-plugin
    • Labels:
    • Environment:
      Operating System: Linux-CentOS, Windows Server 2003 64bit
      gcc version: 4.4.4

    • Similar Issues:

      Description

      I have recently upgraded hudson to latest jenkins(1.437 and later to 1.439). Ofcourse the migration went pretty smooth, but recently I started facing a problem related the existing build numbers of one particular job. In the Build history(left sidebar of any job page) I am
      seeing duplicate build numbers. Check the first attachment named "duplicate_build_numbers". When you reload the same job page, it displays only one unique build and no duplicate builds. But after a few seconds(may be 3 or 4 secs) the duplicate build is coming up.

      I checked the "builds" directory related to that job and found only one directory related to the build. For the build mentioned in the
      figure I saw only one directory named: "2011-10-16_01-06-08"

      So is there any issue in the way Build History is shown to the users or Am I missing anything ?

        Attachments

        1. Broken Build History.jpg
          96 kB
          Maximilian Kernbach
        2. duplicate_build_numbers.png
          9 kB
          nanda kishore

          Activity

          Hide
          mkernbach Maximilian Kernbach added a comment - - edited

          Still occurs in Jenkins v1.472. So.. as I asked three months ago.. What information are needed that we can fix this annoying bug? Jenkins is currently not usable for me. (I'm only using 3 "broken" projects instead of 20-25 as I want to)

          Show
          mkernbach Maximilian Kernbach added a comment - - edited Still occurs in Jenkins v1.472. So.. as I asked three months ago.. What information are needed that we can fix this annoying bug? Jenkins is currently not usable for me. (I'm only using 3 "broken" projects instead of 20-25 as I want to)
          Hide
          mkernbach Maximilian Kernbach added a comment - - edited

          (Comment to Attachment Broken Build History.jpg)
          Current Build-Numbers :
          Server: # 51
          Gerrit DevTest Build #793
          Project "Nightly DevTest Build" is DEACTIVATED, but also showing up on build history!

          Show
          mkernbach Maximilian Kernbach added a comment - - edited (Comment to Attachment Broken Build History.jpg) Current Build-Numbers : Server: # 51 Gerrit DevTest Build #793 Project "Nightly DevTest Build" is DEACTIVATED, but also showing up on build history!
          Hide
          aranega Eduardo Aranega added a comment -

          Can you please confirm if this has been fixed using a different Bug# if yes, do you know the number? Thanks.

          Show
          aranega Eduardo Aranega added a comment - Can you please confirm if this has been fixed using a different Bug# if yes, do you know the number? Thanks.
          Hide
          docwhat Christian Höltje added a comment -

          Over in JENKINS-15156 I mentioned I wrote a tool in ruby for analyzing and fixed build history problems: https://github.com/docwhat/jenkins-job-checker

          If you run jobber.rb with --solve it'll try to fix problems, otherwise it just prints out how it would have solved the problem (in addition of a description of the problem(s)).

          You have to restart Jenkins (or better yet, run it while Jenkins is down) afterwards. A "reload from disk" may also work instead as well.

          Show
          docwhat Christian Höltje added a comment - Over in JENKINS-15156 I mentioned I wrote a tool in ruby for analyzing and fixed build history problems: https://github.com/docwhat/jenkins-job-checker If you run jobber.rb with --solve it'll try to fix problems, otherwise it just prints out how it would have solved the problem (in addition of a description of the problem(s)). You have to restart Jenkins (or better yet, run it while Jenkins is down) afterwards. A "reload from disk" may also work instead as well.
          Hide
          hosc4603 Holger Schmidt added a comment -

          We had the same issue on v1.480.3.
          My analyzis showed the following:
          The actual job was copied via the Jenkins UI.
          After a Jenkins reboot the wrong job history showed up.
          This wrong history was the old history from the original Job.
          The build folder of the new job practically contained the build history of the original and the new job.
          Since the old job had the higher build number those were taken by the Jenkins UI.
          This also explains the older date

          Show
          hosc4603 Holger Schmidt added a comment - We had the same issue on v1.480.3. My analyzis showed the following: The actual job was copied via the Jenkins UI. After a Jenkins reboot the wrong job history showed up. This wrong history was the old history from the original Job. The build folder of the new job practically contained the build history of the original and the new job. Since the old job had the higher build number those were taken by the Jenkins UI. This also explains the older date

            People

            • Assignee:
              Unassigned
              Reporter:
              madhavbnk nanda kishore
            • Votes:
              5 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated: