[users at bb.net] BuildBot multi master helm chart

Pierre Tardy tardyp at gmail.com
Mon Apr 27 08:22:47 UTC 2020

Le lun. 27 avr. 2020 à 09:03, Olaf Radicke <briefkasten at olaf-radicke.de> a
écrit :

> Thanks Pierre, for your comments and explanations.
> > Yes, it is the code name for buildbot 0.9+ which introduced
> > rest api and message queues for everything.
> So, the worker is communicat with a message queue and not
> more direct with the masters? Will the workers have unique
> logins again? So that we get the same problem with the
> static configuration of the replicasets?

No, message queues are for other events than worker to master protocol
(build finished, change created, etc)

> > Pierre Tardy <tardyp at gmail.com> hat am 27. April 2020 08:13 geschrieben:
> [...]
> > >  Okay if I understand this correctly, the configuration is still
> > >  very static.
> > >
> > >
> https://github.com/Zempashi/buildbot_kubernetes_deployment/blob/master/kubernetes/buildbot-master.cfg.yml
> > >
> > >  Here in lines 25 to 31 BuildBot gets the value for the configuration
> > >  from the environment variable. Correct?
> > >
> > >  Who tells BuildBot that the environment variable has changed?
> > Environment variables cannot change dynamically.
> I'm aware of that. What are our options?
> [snip]

In my previous email I was more talking on the general way of how to handle
change of config and reload.
For me this is a real issue, but the change on the number of workers is
more dynamic than change of config, which happens less often.

The simple way of resolving the problem on number of workers, is to just
pre-configure the maximum number of workers.
This is no problem for buildbot if a worker is configured, but not actually

Then, instead of using the basic worker kind I would suggest to use the
kubernetes latent worker.

This will create worker on demand, according to build requests, and also
have the possibility for the build request to dynamically choose which
image to use.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/users/attachments/20200427/4bb8400e/attachment.html>

More information about the users mailing list