Repository files navigation

Buildbot master configuration forbuildbot.python.org.

The production server uses /etc/buildbot/settings.yaml configuration file whichcontains secrets like the IRC nickname password.

Run locally:

make git-update-requirements

Create a PR. Merge the PR. The new venv will be recreated automatically on theserver.

If something goes wrong, commands to recreate the venvmanually on theserver:

make stop-mastergit pullmv venv old-venvmake venvmake start-master# then you may watch logs in realtime:# tail -F master/twistd.log

Upgrading buildbot sometimes requires to run the command:

./venv/bin/buildbot upgrade-master /data/buildbot/master

Make sure that the server is running, and then remove the old virtual environment:

rm -rf old-venv

The buildbot master is hosted on the PSF Infrastructure and is managed viasalt.

psycopg2 also requires libpq-dev:

sudo apt-get install libpq-dev

• Backend host address isbuildbot.nyc1.psf.io.
• The host is behind the PSF HaProxy cluster which is CNAMEd bybuildbot.python.org.
• Database is hosted on a managed Postgres cluster, including backups.
• Remote backups of/etc/buildbot/settings.yaml are taken hourly and retained for 90 days.
• No other state for the buildbot host is backed up!

Configurations from this repository are applied from themaster branch ona*/15 cron interval using theupdate-master target inMakefile.

Python 3.9 is installed manually usingpyenv (which was also installedmanually). Commands to install Python 3.9:

pyenv updatepyenv install 3.9.1pyenv global 3.8.1 3.9.1

The list of workers is stored in/etc/buildbot/settings.yaml on the server.A worker password should be made of 14 characters (a-z, A-Z, 0-9 and specialcharacters), for example using KeePassX.

• Generate a password
• Add the password in/etc/buildbot/settings.yaml
• Restart the buildbot server:make restart-master

Documentation:http://docs.buildbot.net/current/manual/configuration/workers.html#defining-workers