-
Bug
-
Resolution: Fixed
-
Minor
-
1.0.0-rc1
- Core 2.32.3
- 9ac3256
- (no branch)
-
-
Blue Ocean - 1.1-beta-1
Notes
I suspect that there is a race condition between the run being queued and then it no longer being in the queue (backend makes a very academic distinction between runs that are executing and are queued). We need to handle this situation gracefully.
Original request
Steps to reproduce the bug (see video here):
- Create a freestyle job in classic with a bash sleep 10 in it
- Go to its BO version
- Click on Run several times to have jobs queued
- Try to stop one of the queued ones
- Sometimes on stop there is a JS error and the job is not removed
DELETE [http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/blue/rest/organizations/jenkins/pipelines/isa/queue/578/] 404 (Not Found)
request @ blueocean.js:2602
dedupe @ blueocean.js:7854
dedupe @ blueocean.js:7877
rawFetch @ blueocean.js:2620
fetch @ blueocean.js:2695
removeFromQueue @ blueocean.js:5026
_onStopClick @ blueocean.js:1944
onClick @ blueocean.js:2020
invokeGuardedCallback @ blueocean.js:88000
executeDispatch @ blueocean.js:80124
executeDispatchesInOrder @ blueocean.js:80144
executeDispatchesAndRelease @ blueocean.js:79601
executeDispatchesAndReleaseTopLevel @ blueocean.js:79612
forEachAccumulated @ blueocean.js:94269
processEventQueue @ blueocean.js:79788
runEventQueueInBatch @ blueocean.js:88058
handleTopLevel @ blueocean.js:88069
handleTopLevelImpl @ blueocean.js:88136
perform @ blueocean.js:93653
batchedUpdates @ blueocean.js:87336
batchedUpdates @ blueocean.js:91552
dispatchEvent @ blueocean.js:88213
When reloading the page the builds we were trying to stop are either stopped or completed
