-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Duplicate
-
Component/s: workflow-cps-plugin
-
Labels:None
-
Environment:jenkins:latest docker image
-
Similar Issues:
-
Epic Link:
This problem can be reproduced with a simple pipeline job that does nothing but echo and sleep in a loop.
1) Start a run of the pipeline job, the job produces output in the Console Output as I expect
2) Put Jenkins in "Preparing for Shutdown" mode. The jobs stop producing output. That's somewhat surprising, as runs that were started before entering Shutdown Mode are usually allowed to complete.
3) Cancel "Shutdown Mode." The job is still "stuck" and doesn't produce any output. The job also cannot be canceled except by a "hard kill," i.e. going through the "Forcibly terminate running steps" and "Forcibly kill entire build" links
The behavior in #2 is surprising, but not really a problem for me. However, the fact that entering and leaving shutdown mode completely hoses running jobs is really bad. This is compounded by an init.groovy script we use that places Jenkins in shutdown mode at startup.
- blocks
-
JENKINS-32015 Stop Groovy code execution during quietingDown
-
- Resolved
-
- duplicates
-
JENKINS-34256 Preparing Jenkins For Shutdown Hangs Running Pipelines
-
- In Review
-
- is related to
-
JENKINS-49365 Resuming of pipelines vs. docker.image(...).inside(...)?
-
- Reopened
-
-
JENKINS-34256 Preparing Jenkins For Shutdown Hangs Running Pipelines
-
- In Review
-
ad #2 pipeline stops/freezes instead of expected and documented (e.g. also in UI "Manage Jenkins > Prepare for Shutdown") finishing of job:
ad #3 pipeline does not wake up after canceling the shutdown mode:
While (resumable, i.e. non-docker.image(...).inside(...)-dependent) pipelines resume fine after a restart, there is a remainder in "build executor status" that (after the pipeline has finished) requires the workaround to abort it (the finished pipeline) by pressing the 'x' that in turn then asks "Are you sure you want to abort null?":