Details
-
Bug
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Fixed
Description
Hi,
We found a potential bug that can only be replicated in pipeline jobs. Essentially when a job a running and a Jenkins restart occurs, the job is left hanging infinitely:
Resuming build at Tue Jan 03 10:37:18 UTC 2017 after Jenkins restart Waiting to resume part of TestRun2 #2: Waiting for next available executor Waiting to resume part of TestRun2 #2: Waiting for next available executor Waiting to resume part of TestRun2 #2: Waiting for next available executor Waiting to resume part of TestRun2 #2: Waiting for next available executor Waiting to resume part of TestRun2 #2: Waiting for next available executor Waiting to resume part of TestRun2 #2: Waiting for next available executor Waiting to resume part of TestRun2 #2: Waiting for next available executor ...
I noticed that this behaviour does not exhibit on any other job types. i.e. freestyle.
Here is a simple test pipeline script:
node('XXXXX') { stage 'Stage 1' println 'Deploying to Stage 1...' stage 'Stage 2' println 'Running Tests in Stage 2' sleep 120 println 'Tests passed!' stage 'Stage 3' println 'Deploying to Stage 3...' }
...Restart Jenkins as soon as it enters Stage 2, to replicate such behaviour.
Currently I am using version 2.3, but I believe this issue was replicated in previous versions.
Please can you help me explain why this behaviour only exists in pipeline jobs?
Kind Regards,
Tuan
Attachments
Issue Links
- links to
derng I ran 2.32.2 on a fresh home dir (Linux / Java 8), installed Pipeline incl. workflow-basic-steps 2.3, workflow-cps 2.26, pipeline-stage-step 2.2, workflow-job 2.9, created a Pipeline job with the script
ran *Build Now*, waited for the stage view to show the second stage in progress, used /restart to restart Jenkins, and after the restart it completed as expected: