-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins 2.0-rc-1
Running from WAR on Mac
Jenkins 1.651.1 running from WAR on Linux
-
-
workflow-cps 2.78
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?
- duplicates
-
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-
- is related to
-
-
- Resolved
-
-
-
- In Review
-
-
JENKINS-60434 "Prepare for shutdown" should continue executing already running pipelines to completion
-
- Open
-
- links to
[JENKINS-34256] Preparing Jenkins For Shutdown Hangs Running Pipelines
Sam Van Oort
created issue -
Sam Van Oort
made changes -
| Description |
Original:
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: !Screen Shot 2016-04-14 at 3.45.11 PM.png|thumbnail! Those pipeline builds won't show up in the build queue on the main screen. |
New:
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: !Screen Shot 2016-04-14 at 3.45.11 PM.png|thumbnail! 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? |
Sam Van Oort
made changes -
| Assignee | Original: Jesse Glick [ jglick ] | |
| Resolution | New: Cannot Reproduce [ 5 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Daniel Ruoso
made changes -
| Resolution | Original: Cannot Reproduce [ 5 ] | |
| Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
Daniel Ruoso
made changes -
| Summary | Original: Preparing Jenkins 2 For Shutdown Hangs Running Pipelines | New: Preparing Jenkins For Shutdown Hangs Running Pipelines |
Daniel Ruoso
made changes -
| Labels | Original: 2.0 2.0-rc testfest | New: 2.0 2.0-rc lts testfest |
Daniel Ruoso
made changes -
| Environment |
Original:
Jenkins 2.0-rc-1 Running from WAR on Mac |
New:
Jenkins 2.0-rc-1 Running from WAR on Mac Jenkins 1.651.1 running from WAR on Linux |
Daniel Ruoso
made changes -
| Labels | Original: 2.0 2.0-rc lts testfest | New: 1.651.1 2.0 2.0-rc lts testfest |
Sam Van Oort
made changes -
| Assignee | New: Sam Van Oort [ svanoort ] |
Sam Van Oort
made changes -
| Link |
New:
This issue duplicates |
Sam Van Oort
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Reopened [ 4 ] | New: Resolved [ 5 ] |