Documents the second runner and the job order

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-19 14:58:56 +02:00
co-authored by Claude Opus 5.5
parent 0eec9a4ea0
commit 62a88e12f5
3 changed files with 23 additions and 2 deletions
@@ -29,7 +29,7 @@ Text alternative: feature branches go through a pull request with CI into master
| # | Decision | Source |
|---|---|---|
| D1 | **CI**: Gitea Actions on the existing global runner `raspberry-pi-arm64` (labels `linux-arm64`, `ubuntu-latest`; Podman). | Q2 = A, Q3 = A, CQ5 |
| D1 | **CI**: Gitea Actions on the global runner `raspberry-pi-arm64` (always on; Podman), plus since 2026-10-19 a second global runner on the owner's PC (`bryan-desktop-podman`, x64). Labels per property (`linux`, `arm64`/`x64`, `podman`, machine name); `check` and `lighthouse` run on any `linux` runner, deploys only on `raspberry-pi`, and the job order makes a single runner deploy before Lighthouse. See deployment-instructions 1.1. | Q2 = A, Q3 = A, CQ5; owner 2026-10-19 |
| D2 | **Branching**: `master` + short-lived `feature/*` + `release/*`, no `develop` (trunk-based with release branches). Releases are merged back into `master` and tagged `vX.Y.Z` there. | CQ1 |
| D3 | **Environments**: test and production. | Q5 = B |
| D4 | **Test deploy**: automatically on every push to `master` (incl. a merged PR), and manually from any branch with "Deploy to Test", for example to try a branch before merging. | Q6 = B, CQ1 |