Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
Jenkins 2.0-rc-1
Running from WAR on Mac
Jenkins 1.651.1 running from WAR on Linux
-
-
workflow-cps 2.78
Description
Start a couple long-running pipelines with
node {
sleep 100
}
Queue up a few more jobs. Go to "manage jenkins" and "prepare for shutdown."
Now pipeline jobs that would finish and unenqueue never finish and have to manually be killed (which does work). Freestyle jobs complete normally. Queued jobs aren't run, so that part of prepare-for-shutdown works.
Even stranger: upon killing and restarting with Ctrl+C, we get this lovely conundrum:
Those pipeline builds won't show up in the build queue on the main screen.
Checks to do:
- Regression in core?
- Regression in pipeline?
- does /safeRestart or /restart trigger it?
Attachments
Issue Links
- duplicates
-
JENKINS-34281 Queue isn't saved on any shutdown
-
- Resolved
-
- is duplicated by
-
JENKINS-38316 Entering, then cancelling, quiet mode causes builds to hang
-
- Resolved
-
- is related to
-
JENKINS-38316 Entering, then cancelling, quiet mode causes builds to hang
-
- Resolved
-
-
JENKINS-51215 Timeouts suspending pipeline executions (that are already suspended?)
-
- In Review
-
-
JENKINS-60434 "Prepare for shutdown" should continue executing already running pipelines to completion
-
- Open
-
- links to
dnusbaum could you clarify whether this same logic/behavior also applies to the restart that happens after plugin installation (when checking the "Restart Jenkins when installation is complete and no jobs are running" checkbox) or when clicking the Restart Safely button under Manage Jenkins (i.e., the /safeRestart URL, as enabled by https://plugins.jenkins.io/saferestart)? Do running pipeline jobs get paused in those circumstances too and now (with Pipeline: Groovy 2.78) automatically resumed once Jenkins is back up?