Hi, Thank you for your reply! Is there any way to customize what oversubscribed means? We already use a locking mechanism, but still this translates into having multiple running builds that just wait for the locks for several hours. Ideally, I would like to avoid this.
Also, by any chance, can you read a lock value from the canStartBuild function? Thank you! Vlad Bogolin On Fri, Jul 1, 2022 at 12:40 PM Povilas Kanapickas <povi...@radix.lt> wrote: > Hi Vlad, > > You could setup a number of master locks that are each assigned to a > particular physical machine. Then you can setup renderable locks for > builds: a build would look into what physical machine it's about to > launch on and select the correct lock. If the physical machine is > oversubscribed, Buildbot will notice that lock can not be acquired look > for another worker for the build. > > Regards, > Povilas > > On 2022-06-28 12:44, Vlad Bogolin wrote: > > Hello, > > > > We are using buildbot with primary DockerLatentWorkers for our CI. So, > > given a physical machine, we have several DockerLatentWorkers that may > > run on it. While this works well, in some cases buildbot starts too many > > latent workers on the same machine. Is there a way to limit starting > > builds for a particular DockerLatentWorker if others are already running > > on the same machine? > > > > I feel like this should be achievable using the canStartBuild, but I am > > unsure how. Is it possible to access the full list of defined latent > > workers and see if one is on or not in the canStartBuild function? > > > > Thank you! > > Vlad Bogolin > > > > _______________________________________________ > > users mailing list > > users@buildbot.net > > https://lists.buildbot.net/mailman/listinfo/users > > > -- Vlad
_______________________________________________ users mailing list users@buildbot.net https://lists.buildbot.net/mailman/listinfo/users