unable to abort a build using workflow plugin

68 views
Skip to first unread message

Chris Taclas

unread,
Feb 19, 2015, 1:11:53 PM2/19/15
to jenkins...@googlegroups.com
Hi all,

I have a jenkins job set up using the workflow plugin. I was trying to set up some parallel build steps. There may have been a problem with the way I had originally configured this, but my system is in a state where I have two instances of my workflow running, they're stuck, and aborting the job seems to have no effect. Is there a way to force kill these processes?


The thread dump page has this:

Executor #-1 for master : executing Mob_Rent_Workflow_iOS_temp #2

"Executor #-1 for master : executing Mob_Rent_Workflow_iOS_temp #2" Id=471113 Group=main TIMED_WAITING on java.util.concurrent.atomic.AtomicBoolean@1efc81b1
	at java.lang.Object.wait(Native Method)
	-  waiting on java.util.concurrent.atomic.AtomicBoolean@1efc81b1
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.waitForCompletion(WorkflowRun.java:205)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:178)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)
	at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43)

Executor #-1 for master : executing Mob_Rent_Workflow_iOS_temp #4

"Executor #-1 for master : executing Mob_Rent_Workflow_iOS_temp #4" Id=476932 Group=main TIMED_WAITING on java.util.concurrent.atomic.AtomicBoolean@26cc0f3d
	at java.lang.Object.wait(Native Method)
	-  waiting on java.util.concurrent.atomic.AtomicBoolean@26cc0f3d
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.waitForCompletion(WorkflowRun.java:205)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:178)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)
	at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43)

Stefan Thomasson

unread,
Feb 23, 2015, 2:56:40 AM2/23/15
to jenkins...@googlegroups.com
Hi,
I am also wondering about this, it does not help restarting jenkins as the jobs are resumed automatically.

For me it was caused by starting the same job with identical parameters.
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2e3b2017-f6cb-4e3d-a55b-e31c3d47eabd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jesse Glick

unread,
Feb 26, 2015, 12:03:06 PM2/26/15
to jenkins...@googlegroups.com
On Thursday, February 19, 2015 at 1:11:53 PM UTC-5, Chris Taclas wrote:
There may have been a problem with the way I had originally configured this

So some bug in Workflow, possibly filed, possibly not.

Is there a way to force kill these processes?

See the workaround mentioned here: https://issues.jenkins-ci.org/browse/JENKINS-25550 
Reply all
Reply to author
Forward
0 new messages