verm__ changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.5.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | irclogs: https://libera.irclog.whitequark.org/buildbot
vmeson has quit [Ping timeout: 276 seconds]
vmeson has joined #buildbot
Guest2550 has joined #buildbot
<Guest2550> hi i try to start a build-run on one worker multiple times but i get one started run, and one pending run .. i increased the max_builds for the worker but this seems to only increase the number of different Build(Facrories) i can start concurrently
<Guest2550> i have a bulder that triggers a lof of other builds but does not do much itself - i would like to start/trigger these without constraint .. if not enough workers are available for the triggered builds thats fine they can wait for there turn
<Guest2550> but i can get the config right :(
<Guest2550> can _not_ :)
<Guest2550> ah http://docs.buildbot.net/current/manual/configuration/workers.html "In Worker For Builders concept only one build from the same builder would run on the worker." it seems thats not possible at all :/
<felixfontein> if you have the same build several times in the same queue, it will be collapsed into one
<felixfontein> if you set `'collapseRequests': False` for a builder, it won't do that
<Guest2550> yes i did that
<Guest2550> but on one worker istill cant start the same builde concurrently
<Guest2550> now i try to make a lock that puts all but my starter-(forcescheduler) -builder in one workerlock and my starter-builder intto another workerlock with max_build=2 for all worker but currently that is not really working how i want it to
Guest2550 has quit [Quit: Client closed]
Ilusi has joined #buildbot
kveremitz has quit [Ping timeout: 248 seconds]