-
Bug
-
Resolution: Fixed
-
Major
-
1.509.3 or trunk
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.
- is related to
-
JENKINS-16194 Delete the oldest build but it still come up on HistoryWidget
-
- Resolved
-
[JENKINS-19920] After deleting last build, next build of last build is zombie
Link |
New:
This issue is related to |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Labels | Original: lazy-loading | New: lazy-loading lts-candidate |
Labels | Original: lazy-loading lts-candidate | New: 1.532.1-fixed lazy-loading |
Workflow | Original: JNJira [ 151441 ] | New: JNJira + In-Review [ 193932 ] |