docs/services/buildbot: update for nomad

void-linux · Jul 14, 2024 · e1fded5 · e1fded5
1 parent c8c82b7
commit e1fded5
Showing 1 changed file with 23 additions and 6 deletions.
diff --git a/docs/src/services/buildbot.md b/docs/src/services/buildbot.md
@@ -2,13 +2,13 @@
 
 BuildBot is our legacy build scheduler.
 
-The buildbot master runs at
+The buildbot controller runs at
 [build.voidlinux.org](https://build.voidlinux.org) and provides
 unified scheduling to all other build tasks in the fleet.  BuildBot
 also exposes a web interface.
 
 The current status of the build infrastructure can be found on the
-build waterfall.  This view shows what each of the buildslaves is
+build waterfall.  This view shows what each of the builders is
 doing right now, and uses traffic light colors for build state.  A
 purple builder is usually a reason to contact void-ops and figure out
 what's wrong with the build host.
@@ -18,7 +18,7 @@ failed without needing to push a new commit.  Not all committers have
 access to restart failed builds this way.  If you believe that you
 should have this access, contact maldridge@.
 
-## Moving a buildslave
+## Moving a builder
 
 Don't.
 
@@ -28,8 +28,25 @@ to be moved is on the musl cluster, all musl builders will need to be
 moved with it.  Similarly, the aarch64 builders must always move as a
 pair.
 
+## Updating buildbot
+
+The buildbot controller and builders should be kept at the same buildbot
+version.
+
+1. Update the buildbot version in both the `buildbot` and
+   `buildbot-builder` Dockerfiles.
+2. Rebuild the service containers by triggering a build for the
+   `infra-buildbot` and `infra-buildbot-builder` containers in CI.
+3. Using the updated container, run `/upgrade.sh` in the
+   `infra-buildbot` container on the buildbot controller machine with
+   the buildbot database mounted:
+```sh
+docker run --rm ... ghcr.io/void-linux/infra-buildbot:YYYYMMDDRN /upgrade.sh
+```
+4. Update the nomad jobs to use the new containers and restart them
+
 ## EOL
 
-BuildBot is slated for replacement this fall/winter.  The system will
-be replaced by the Distributed XBPS Package Builder (dxpb) which will
-resolve many of the long standing problems in the buildbot.
+BuildBot is slated for replacement in the future.  The system will
+be replaced by the Distributed XBPS Package Builder (dxpb) or nbuild
+which will resolve many of the long standing problems in the buildbot.