Documents the second runner and the job order
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -930,3 +930,15 @@ Verder heb ik de vraag ook beantwoord"
|
||||
**Context**: OPERATIONS - Deployment pipeline adjustment (during Monitoring Setup approval wait)
|
||||
|
||||
---
|
||||
|
||||
## Deployment - Runner Tests
|
||||
|
||||
**Timestamp**: 2026-10-19T12:58:55Z
|
||||
|
||||
**User Input**: "In theorie kan de raspberry pi de lighthouse nog wel runnen toch? De raspberry pi runne ris namelijk de hoofdrunner die altijd aan staat en alles moet kunnen runnnen anmelijk"
|
||||
|
||||
**AI Response**: "Confirmed: the Pi has every label the workflow uses (linux for check/lighthouse, raspberry-pi for deploys) with the same job image as before. Test results: run 538 (PR, 0eec9a4) failed: lighthouse on the PC runner, chrome-launcher treated the container as WSL (is-wsl sees 'microsoft' in the shared WSL kernel; is-docker 2.2.1 only checks /.dockerenv, which Podman does not create) and tried /mnt/undefined/Users/undefined/AppData/Local. Fixed in the PC runner config (empty /.dockerenv via --volume /dev/null:/.dockerenv:ro), not in the project; also fixed start-runner.ps1 (PowerShell 'if (podman container exists)' tested output, not exit code, so the old container was never replaced). Run 539 (dispatch, both runners): check Pi, deploy-test Pi in parallel with lighthouse on the PC, all green. Run 540 (dispatch, PC runner stopped): Pi ran check, then deploy-test, then lighthouse, all green. PC runner restarted. Updated deployment-instructions 1.1 and deployment-plan D1. Docs committed locally, not pushed (a push starts another full run); commit/push permission for this change ends here."
|
||||
|
||||
**Context**: OPERATIONS - Deployment pipeline adjustment verified
|
||||
|
||||
---
|
||||
|
||||
+10
-1
@@ -28,7 +28,16 @@ In Gitea, under **Repository → Settings → Actions**:
|
||||
| `HEALTH_CHECK_URL_PRODUCTION` | `https://andreaslop.nl/` | no; set it only once the DNS points to the new host |
|
||||
| `FTP_REMOTE_DIR` | `wwwroot` | no; default `wwwroot` |
|
||||
|
||||
Check that Actions is enabled for the repository. The global runner `raspberry-pi-arm64` picks up `runs-on: ubuntu-latest`.
|
||||
Check that Actions is enabled for the repository. Two global runners, each job image `gitea/runner-images:ubuntu-latest`. A job runs on a runner that has **all** its `runs-on` labels.
|
||||
|
||||
| Runner | Labels | Always on | Runs |
|
||||
|---|---|---|---|
|
||||
| `raspberry-pi-arm64` (systemd service `gitea-runner`, config `/etc/gitea-runner/config.yaml`) | `global`, `linux`, `arm64`, `podman`, `raspberry-pi`, plus `ubuntu-latest` and `linux-arm64` for older workflows | yes | everything |
|
||||
| `bryan-desktop-podman` (Podman machine on the owner's PC, `C:\Users\Bryan\gitea-runner\`) | `global`, `linux`, `x64`, `podman`, `bryan-desktop` | no | `check` and `lighthouse` when it is free |
|
||||
|
||||
`check` and `lighthouse` use `runs-on: linux`, the deploys `runs-on: raspberry-pi`. `deploy-test` is listed above `lighthouse` in the workflow: Gitea hands out waiting jobs in that order, so a single free runner deploys first, while two runners deploy and run Lighthouse at the same time.
|
||||
|
||||
Notes for the PC runner: its job containers share the WSL kernel, so the runner mounts an empty `/.dockerenv` (otherwise `is-wsl` in chrome-launcher treats the container as WSL and Lighthouse fails). Container actions (`uses:` of a Docker action) do not work on Podman; that is one reason deploys stay on the Pi.
|
||||
|
||||
### 1.2 Test server (Raspberry Pi with nginx)
|
||||
The current WordPress site runs on the same Pi. The test site gets its **own folder** and its **own nginx block**, and touches nothing of WordPress.
|
||||
|
||||
@@ -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 |
|
||||
|
||||
Reference in New Issue
Block a user