Re: Prevent job from when a particular job is running

2013-08-19 Thread Daniel Beck
Yes, it's the number of executors. Of course, this requires jobs a and b to run on the same node, and prevents jobs c, d, ... from running on that node (or they'll block/be blocked by a and b). On 19.08.2013, at 18:35, Jared Griffith wrote: > Isn't there already a native configuration option t

Re: Prevent job from when a particular job is running

2013-08-19 Thread Jared Griffith
Isn't there already a native configuration option that works per node on how many concurrent builds each can run? On Mon, Aug 19, 2013 at 12:29 AM, Steffen Breitbach < steffen.breitb...@1und1.de> wrote: > Hi Jared! > > > Is there a way to prevent job b from running if job a is running? > > Besid

AW: Prevent job from when a particular job is running

2013-08-19 Thread Steffen Breitbach
Hi Jared! > Is there a way to prevent job b from running if job a is running? Beside the other solution you might want to give the "Throttle Concurrent Builds" plugin a look. Regards Steffen -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group.

Re: Prevent job from when a particular job is running

2013-08-16 Thread Jared Griffith
Perfect, that's exactly what I was looking for! Thanks. On Fri, Aug 16, 2013 at 1:31 PM, Baptiste Mathus wrote: > Well, a job is allowed to have many upstream jobs, so that might still > work. > > If not, then see > https://wiki.jenkins-ci.org/display/JENKINS/Build+Blocker+Plugin > > Cheers >

Re: Prevent job from when a particular job is running

2013-08-16 Thread Baptiste Mathus
Well, a job is allowed to have many upstream jobs, so that might still work. If not, then see https://wiki.jenkins-ci.org/display/JENKINS/Build+Blocker+Plugin Cheers Le 16 août 2013 22:26, "Jared Griffith" a écrit : > Yeah, I was thinking about that. However, in this particular instance, > job

Re: Prevent job from when a particular job is running

2013-08-16 Thread Jared Griffith
Yeah, I was thinking about that. However, in this particular instance, job b is actually a downstream job of say, job f. I might have to figure something else out here. Thanks. On Fri, Aug 16, 2013 at 12:59 PM, Baptiste Mathus wrote: > Yup. You might want to just specify a as an upstream job

Re: Prevent job from when a particular job is running

2013-08-16 Thread Baptiste Mathus
Yup. You might want to just specify a as an upstream job in b configuration. Then check the box "block this build when upstream builds are running" (approximate text). But, you'll have to note that this will actually create a dependency between b and a, meaning the end of "a" build will trigger o

Prevent job from when a particular job is running

2013-08-16 Thread Jared Griffith
Is there a way to prevent job b from running if job a is running? -- Jared Griffith Linux Administrator, PICS Auditing, LLC P: (949) 936-4574 C: (909) 653-7814 17701 Cowan #140 | Irvine, CA | 92614 Join PICS on LinkedIn and Twitter!