How to remove tight pipe work in Jenkins?

Question

I use the Pipeline plugin collection (formerly Workflow) for Jenkins. I somehow managed to create a workflow on my Jenkins server that I cannot stop. Querying current stack traces with Thread.getAllStackTraces().keySet().each() { t -> println(t.getName())} does not return any output artists matching this job. In addition, if this is the only living task in the Build Artist Status window, then there are no artists at all.

Restarting the slave in which the task was performed did not affect. Restarting the Jenkins master server did not affect either. Any thoughts on how I can get rid of this thing?

Answer 1

I was able to stop work by sending a POST request: http://jenkins.fqdn:8080/job/$JobName/branch/$BranchName/8/term (Note the variables $ JobName and $ BranchName)

I found this URI by doing the following:

• Click on the number next to the task to go to that exact task.
• Click the "Output Console" link.
• Right-click the "Click here to force shutdown" link.
• Select the "Inspect" menu item. (This is in Chrome, configure this step for your preferred browser)
• Copy the URI from the Ajax.Request call. For example: onclick="new Ajax.Request(' http://jenkins.fqdn:8080/job/$JobName/branch/$BranchName/8/term '); false"

For some reason, clicking the Click here to forcibly terminate running steps link did not actually complete the job, but manually sent an email request. I suspect this is just a small error in the user interface code.

Answer 2

I have the same problem today, and the workaround from the comment above did not help me, but sent the /kill command instead of /term .

I found a working solution here :

• OPEN https: //your.jenkins.fqdn/script
• PUT Jenkins.instance.getItemByFullName("jobName").getBuildByNumber(9).finish(hudson.model.Result.ABORTED, new java.io.IOException("Aborting build"));
• CLICK "Run"