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 <[email protected]> wrote: > 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 > <[email protected]> wrote: > 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. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > > -- > 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! > > > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
