On Tuesday, May 19, 2015 at 5:58:12 PM UTC+2, Baptiste Mathus wrote: > > Better use the throttle concurrent build plugin IMO. Works fine for us: > > Define a central token. Then configure both job to "acquire" it when > starting. Done. Both jobs won't run at the same time. > This plugin isn't as easy to handle (you've to create a central token) but works as expected, not creating a deadlock if both jobs are queued, but not running, because of all slots occupied.
-- Thomas -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b322b0ae-8eb1-4db9-905b-40ea30f85d4c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
