[ 
https://issues.jenkins-ci.org/browse/JENKINS-11853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160327#comment-160327
 ] 

Maximilian Kernbach commented on JENKINS-11853:
-----------------------------------------------

Still happens in Jenkins 1.455. Can someone please look into it? What 
information is needed to get this issue fixed? 
                
> 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

        

Reply via email to