-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 10.9
integrity plugin 2.0.1
We got some pipeline jobs which are impossible to kill. After pressing the red 'x' Button we get the following output:
[...] [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] End of Pipeline Finished: SUCCESS Resuming build at Wed Feb 15 07:47:17 CET 2017 after Jenkins restart Ready to run at Wed Feb 15 07:47:19 CET 2017 Resuming build at Wed Feb 15 07:50:34 CET 2017 after Jenkins restart Ready to run at Wed Feb 15 07:50:35 CET 2017 Aborted by User Click here to forcibly terminate running steps
The main problem is, that the build succeeded but tried to restart after a jenkins restart. Clicking the 'terminate' message does not work. Are they suggestions how to kill those 'zombie' pipelines?
[JENKINS-42049] How to kill unstoppable zombie pipeline jobs
Simon Beyer
created issue -
Simon Beyer
added a comment - Actually about 2-3 hours after posting this there was a Pipeline Plugin update. Now there are more options (and finally) any response after hitting the "kill" button. Now I can kill the process. The handling is kind of buggy but it works.
Simon Beyer
added a comment - Actually about 2-3 hours after posting this there was a Pipeline Plugin update. Now there are more options (and finally) any response after hitting the "kill" button. Now I can kill the process. The handling is kind of buggy but it works. Simon Beyer
added a comment - Newest pipeline job fixed the inaction of the "kill" button Simon Beyer
made changes -
| Assignee | New: Simon Beyer [ swanh ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
I have an unstoppable job that has been running for 7 days. I couldn't stop it via UI, by Jenkins restart.
Job failed with " No space left on device" error and continue has status "running".
See 
and 
Jenkins 2.46.1
| Resolution | Original: Fixed [ 1 ] | |
| Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
| Attachment | New: Screen Shot 2017-04-14 at 9.30.41 AM.png [ 37144 ] |
| Attachment | New: Screen Shot 2017-04-14 at 9.31.51 AM.png [ 37145 ] |
Ilia Shakitko
added a comment - Same with me, but "killing/stopping" a hanged job doesn't work - no reaction...
Ilia Shakitko
added a comment - Same with me, but "killing/stopping" a hanged job doesn't work - no reaction...
Hi Simon,
On the face of it, this looks more like a pipeline problem. Usually pipeline builds should resume an _unsuccessful _ job after a jenkins restart.
Is Jenkins restart a frequent scenario for you? How about letting the first pipeline batch just run through after the jenkins restart, instead of trying to abort them? Does the pipeline after restart just gets stuck somewhere?
There is infact an open feature request on pipeline for this: https://issues.jenkins-ci.org/browse/JENKINS-33761.
Regards,
Anurag.