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

Review updated packages, pay attention to buildbot updates. Create a PR. Mergethe PR. The new venv will be recreated automatically on the server.

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.

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

To test a change to the buildbot code locally, a worker is needed to run jobs.First create asettings.yaml file in the repository root. The settings file controlshow the Builbot master should connect to workers. The simplest setup runs a worker in thesame process as the Buildbot master on the local machine. The local environment must have anyrequired dependencies for that worker environment. With the settings file created run:

export PYBUILDBOT_SETTINGS_PATH=$(pwd)/settings.yaml

Then, update the settings file to include the following:

# Use a local in-process workeruse_local_worker:true# Use one of the buildfactories found in master/custom/factories.py.# Here we use the WASI cross build factory. If unspecified, the default# is to use the UnixBuild factorylocal_worker_buildfactory:"Wasm32WasiCrossBuild"

Then run

make update-master

This updates the state database and starts the buildbot master.You can now openhttp://localhost:9011/ and use the local Buildbot master web UI.Under Builds -> Builders there should be one or more builders for the factorythat was configured. After clicking on the relevant builder, clicking on the "force"button in the upper right corner will start a new build.

Finally, the master can be stopped when no longer needed by running

make stop-master