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

After deleting last build, next build of last build is zombie




      If you have a project with several builds, delete the last one, then go to the new last build (the former penultimate build) and ask for its next build, you get the now-deleted last build back! At least in the API; from the UI, you have a Next Build link which gives a 404. This is a symmetric bug from JENKINS-16194, and is caused by the abuse of selfReference to mean also "no such build".

      While reproducing this in a unit test I found another deletion-related bug: AbstractLazyLoadRunMap.numberOnDisk does not get updated when a build is deleted. The symptom is that after the deletion of the last build, say #2, the project's last build will correctly be reported as #1—but a fresh copy which is not equals to the original. The presence of two copies of the "same" build can cause mayhem.


        Issue Links


            jglick Jesse Glick created issue -
            jglick Jesse Glick made changes -
            Field Original Value New Value
            Link This issue is related to JENKINS-16194 [ JENKINS-16194 ]
            jglick Jesse Glick made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            jglick Jesse Glick made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Resolved [ 5 ]
            jglick Jesse Glick made changes -
            Labels lazy-loading lazy-loading lts-candidate
            olivergondza Oliver Gondža made changes -
            Labels lazy-loading lts-candidate 1.532.1-fixed lazy-loading
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 151441 ] JNJira + In-Review [ 193932 ]


              jglick Jesse Glick
              jglick Jesse Glick
              0 Vote for this issue
              3 Start watching this issue