Where Does Buildbot Store Master Config?
Buildbot master basedir and config file paths on Linux for self-hosted continuous integration setups.
Last updated
Buildbot keeps master state in a basedir folder. That folder holds master.cfg with builders, schedulers, and workers. A sqlite or Postgres database beside it tracks build history and logs.
Workers keep only build sandboxes that recreate on demand. The master basedir is the part to back up. Copy it with the database for moves. Config changes apply with a reconfig without restarting builds. Change sources poll repos on timers. Trial runs validate configs without touching production. Remote workers need open ports.
Where Buildbot stores this, by platform
/var/lib/buildbot/master
Builder configs, database, and logs for the master. Check the systemd unit when missing since basedir varies. Copy with the master stopped.
/var/lib/buildbot/master/master.cfg
Builders, schedulers, and worker passwords in Python code. Test with buildbot checkconfig before reloading. Keep in version control.
Frequently asked questions
what do i back up for a Buildbot master move
Copy the master basedir with master.cfg and the database. The config holds builders and schedulers. The database tracks build history. Both restore the master.
where is the Buildbot master directory
Open master.cfg in the basedir to read builder and worker blocks. Common spots are /var/lib/buildbot/master and /srv/buildbot. The systemd unit shows the active basedir.
Notice an outdated path? Let us know.