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

Pierre Tardy tardyp at gmail.com
Mon Apr 27 06:13:07 UTC 2020


> Pierre Tardy <tardyp at gmail.com> hat am 26. April 2020 14:51 geschrieben:
> >
> > We have a blog post in our medium account which describes how to install
> buildbot on kubernetes.
> >
> https://medium.com/buildbot/deploying-buildbot-nine-on-kubernetes-c08422597e75
> Buildbot "nine" currently means the master branch?
Yes, it is the code name for buildbot 0.9+ which introduced rest api and
message queues for everything.

> 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. So there is no way to
watch them.
If you'd like to implement that, you would need to read those parameters in
a configmap, and have a kubernetes watcher able to register to the kube
event stream and reload config after a debounce delay when the config map
is changing. That would be quite neat!

Else, I guess usually you need to do a rolling update of the masters when
the config file or config map is changed.

for a clean shutdown (not start new build, and wait for current builds to
finish) you need to send SIGUSR1 to the masters.
You want to use this signal for rolling updates (and increase the timeouts
a bunch as waiting for build to finish can take a while)


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

More information about the users mailing list