[JIRA] (JENKINS-42049) How to kill unstoppable zombie pipeline jobs
Title: Message Title
Daniel Ruiz commented on JENKINS-42049
Re: How to kill unstoppable zombie pipeline jobs
you can try going to the jenkins script console and execute: Jenkins.instance.getItemByFullName("YOURJOBFULLNAME").getBuildByNumber(YOURJOBBUILDNUMBER).finish(hudson.model.Result.ABORTED, new java.io.IOException("Aborting build")); if it's not working, the only way I found it's deleting the build number folder inside the builds of the job, on master jobs folder. and restarting jenkins. It's a horrible solution, but ...
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42049) How to kill unstoppable zombie pipeline jobs
Title: Message Title Simon Beyer resolved as Fixed Newest pipeline job fixed the inaction of the "kill" button Jenkins / JENKINS-42049 How to kill unstoppable zombie pipeline jobs Change By: Simon Beyer Status: Open Resolved Assignee: Simon Beyer Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed
[JIRA] (JENKINS-42049) How to kill unstoppable zombie pipeline jobs
Title: Message Title Simon Beyer commented on JENKINS-42049 Re: How to kill unstoppable zombie pipeline jobs 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. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42049) How to kill unstoppable zombie pipeline jobs
Title: Message Title PTC ALM commented on JENKINS-42049 Re: How to kill unstoppable zombie pipeline jobs 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. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42049) How to kill unstoppable zombie pipeline jobs
Title: Message Title Simon Beyer created an issue Jenkins / JENKINS-42049 How to kill unstoppable zombie pipeline jobs Issue Type: Bug Assignee: Unassigned Attachments: tmp1.PNG Components: integrity-plugin Created: 2017/Feb/15 7:02 AM Environment: Jenkins 10.9 integrity plugin 2.0.1 Priority: Major Reporter: Simon Beyer 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?
