Skip to content

Update production deploy documentation #1016

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
RazvanLiviuVarzaru merged 1 commit into from
Oct 27, 2026
Merged

Update production deploy documentation #1016

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .github/workflows/bbm_deploy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@ on:
- "validate_master_cfg.sh"
- "worker_locks.yaml"
- "dashboards/**"
- "!**/README.md"
pull_request:
paths:
- ".github/workflows/bbm_deploy.yml"
Expand All @@ -42,6 +43,7 @@ on:
- "validate_master_cfg.sh"
- "worker_locks.yaml"
- "dashboards/**"
- "!**/README.md"

jobs:
check:
Expand Down
16 changes: 16 additions & 0 deletions docker-compose/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,12 +30,28 @@ The [bbm-deploy](../.github/workflows/bbm_deploy.yml) workflow checks the config
cd /srv/prod/docker-compose
docker-compose stop <master>
docker-compose --env-file .env up -d <master>
grep 'BuildMaster is running' logs/<log>.log | tail -n 1
```

Restart the next master once `grep` shows this start's time. `<log>` is the master's directory name: `amd64-master-0` for `autogen_amd64-master-0`.

`stop` gives the master up to its `stop_grace_period` (5 minutes, set in `generate-config.py`) to shut down before it is killed. To make it faster, pass a shorter timeout, in seconds: `docker-compose stop -t 30 <master>`.

Check the number of autogen masters before deploying a change to `os_info.yaml`; see [Autogen masters](../docs/server-builders.md#autogen-masters).

### Stopping and starting the masters

Because of [buildbot#9215](https://github.com/buildbot/buildbot/issues/9215), stop and start the production masters one at a time, and start the next only once the previous one has logged `BuildMaster is running`.

Comment thread
RazvanLiviuVarzaru marked this conversation as resolved.
Resolved
Stop them in this order, and start them in the reverse order, master-libvirt first:

1. master-protected-branches and master-galera, so that no new server or Galera builds start;
1. the autogen masters;
1. master-docker-nonstandard and master-docker-nonstandard-2;
1. master-migration;
1. master-nonlatent;
1. master-libvirt.

### Restarting production without disrupting anyone

Prefer restarting when no branch protection builds are running, so that contributors already have their results on GitHub. Buildbot is meant to restart the builds a stop interrupts, but doesn't always. If you restart while such builds run, check the Grid View, filtered on the `protected` tag, that they finished or were restarted.
Expand Down