Hi Marc,
I ran out of time to get to the root of this - but I'm pretty sure it is an
issue in Jenkins core.
Looks like when a build is scheduled and waitForStart() is called it never
returns if the build is cancelled.
You may want to try with the latest and greatest Jenkins to check its been
It might be related to JENKINS-19656
(https://issues.jenkins-ci.org/browse/JENKINS-19656).
On Friday, 4 April 2014 21:53:08 UTC+1, teilo wrote:
Reproduced the issue locally - but I think the root cause is Jenkins not
the plugin.
On Friday, 4 April 2014 19:04:34 UTC+1, Marc MacIntyre
Looks unrelated to me.
On Monday, 7 April 2014 17:36:11 UTC+1, Schalk Cronjé wrote:
It might be related to JENKINS-19656 (
https://issues.jenkins-ci.org/browse/JENKINS-19656).
On Friday, 4 April 2014 21:53:08 UTC+1, teilo wrote:
Reproduced the issue locally - but I think the root cause
I Changed the handling of cancel since the last release - so that it actually
kills the downstream projects as well (including those in the queue).
Given that there is a good chance that this is fixed - if you feel brave and
want to try a snapshot.
/James
From: jenkinsci-users@googlegroups.com
The latest snapshot doesn't address this; it does abort running subjobs,
and dequeues those that have not started, but if a sub-job is manually
dequeued, the build flow never notices.
On Fri, Apr 4, 2014 at 1:39 AM, James Nord (jnord) jn...@cisco.com wrote:
I Changed the handling of cancel
Reproduced the issue locally - but I think the root cause is Jenkins not
the plugin.
On Friday, 4 April 2014 19:04:34 UTC+1, Marc MacIntyre wrote:
The latest snapshot doesn't address this; it does abort running subjobs,
and dequeues those that have not started, but if a sub-job is manually
