[
https://issues.jenkins-ci.org/browse/JENKINS-11853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161915#comment-161915
]
Igor Mayanov commented on JENKINS-11853:
----------------------------------------
There is much more serious issue visible on the screenshot - take a look at
build dates! Build shown as #44 has wrong number - it was built more than 1
month earlier than builds #42 and #43. Actually this build has different number
(maybe 41 or even smaller), but it was later re-assigned to number 44 because
of strange mistake. Please notice - latest build for this job is #43, and it
was built successfully, however Jenkins displays this job as failed in the jobs
list. We observe this error on our Jenkins build environment (RHEL 6.1) for a
few months, it still happens even in the newest Jenkins release 1.460. This
happens not too often, without any specific time or environment conditions. Can
somebody investigate what happens with Jenkins builds numbering, please?
> Duplicate build numbers in the Build History
> ---------------------------------------------
>
> Key: JENKINS-11853
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11853
> Project: Jenkins
> Issue Type: Bug
> Components: build-pipeline
> Environment: Operating System: Linux-CentOS
> gcc version: 4.4.4
> Reporter: nanda kishore
> Labels: build
> Attachments: duplicate_build_numbers.png
>
>
> 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 ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
