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 one of b. HTH. Cheers Le 16 août 2013 21:12, "Jared Griffith" <[email protected]> a écrit : > 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 > > <http://www.picsauditing.com> > > 17701 Cowan #140 | Irvine, CA | 92614 > > Join PICS on LinkedIn and Twitter! > > <https://twitter.com/PICSAuditingLLC> > > -- > 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.
