[
https://issues.jenkins-ci.org/browse/JENKINS-11853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162621#comment-162621
]
alexlombardi commented on JENKINS-11853:
----------------------------------------
Seeing this issue in Jenkins 1.463 with a job that has a single build entry
when running a Master-Slave setup as a Windows service. Have a single build in
the folder but the entry appears twice in the Build History box (build was
successful in my case though and is really old) in Jenkins about 5 seconds
after I have navigated into the appplication and try to look at build details
(it is NOT there immediately). Do not see this happen with any other projects
but this one.
> 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
> Priority: Critical
> 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
