Hi, On 04/04/12 21:05, Sami Tikka wrote: > If the "lock" you mention below is something provided by the > locks-and-latches plugin, you should consider another way to make sure > only Job A or B runs. Locks-and-latches is unmaintained.
Yes, forgot to include that. It's the locks-and-latches plugin. Thought since it supposedly only exposed the internal resource locking of Jenkins that it wouldn't need much in the line of maintenance. > There is a newer plugin called Throttle Concurrent Builds plugin. > > Another way to do it is to tie A and B to a slave having only 1 executor. > > -- Sami Went with the Throttle Concurrent Builds plugin as you suggested. Seems more configurable than the locks plugin since we only care about preventing more than one build job from a set of 3 running per node, but would be fine with them being run on 3 different nodes. -- Regards, Darragh Bailey
