Hi, The solution should be in custom nextSlave function.
For similar problem, I tried to use custom nextSlave(that should be the natural solution) without success. Currently I am using a 'ugly' combination of "nextBuild" /max_builds Good luck, Ciprian On Thu, Feb 11, 2016 at 2:11 AM, Greg MacDonald <gmacdon...@trionworlds.com> wrote: > Hi Everyone, > > > > Is there a way to limit the number of builds per node for a set of > builders? I’m using a slave lock for that purpose on the builder and it’s > not quite what I’d like to happen. The builds start on a specific slave in > the starting state. But they’re waiting not starting and it makes it > difficult in the UI to see what is currently running. Also I’d rather the > scheduling be performed dynamically at the time slaves become free. Is > there another way to do this? > > > > -Greg > > _______________________________________________ > users mailing list > users@buildbot.net > https://lists.buildbot.net/mailman/listinfo/users >
_______________________________________________ users mailing list users@buildbot.net https://lists.buildbot.net/mailman/listinfo/users
