Runs deploys first and lets a second runner share the work
Continuous Integration / check (pull_request) Successful in 6m0s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Failing after 1m13s
Continuous Integration / deploy-production (pull_request) Skipped

Jobs now pick runners by label: check and Lighthouse run on any Linux runner,
deploys only on the Pi. The test deploy is listed before Lighthouse, so a single
runner deploys first while two runners run both at once.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-19 14:17:12 +02:00
co-authored by Claude Opus 5.5
parent 3b86f04945
commit 0eec9a4ea0
2 changed files with 79 additions and 59 deletions
@@ -918,3 +918,15 @@ Verder heb ik de vraag ook beantwoord"
**Context**: OPERATIONS - Monitoring Setup; PR run green
---
## Deployment - Second Runner and Job Order
**Timestamp**: 2026-10-19T12:17:12Z
**User Input**: "Ik heb de labels aangepast. kan je het controleren? Daarna mag je de aanpassingen voor de workflow doen. dan kunnen we meteen alles testen" (earlier: "Ik wil nog wel de mogelijkheid hebben om ze tegelijk te draaien als ik 2 runners heb, maar als alleen de pi draait of de andere runner nog druk is wil ik dat deploy eerst wordt opgepakt. is dat mogelijk?" and "Dat is nog een issue. MIsschien later te verhelpen of deploys niet op de pc laten doen.")
**AI Response**: "Owner added a second global runner on the PC (bryan-desktop-podman, Podman in WSL, same job image as the Pi, labels global/linux/x64/podman/bryan-desktop). Pi labels verified via API: linux-arm64, ubuntu-latest, global, linux, arm64, podman, raspberry-pi. Gitea 1.27 hands out waiting jobs ordered by (updated, id) and job ids follow the YAML order, and a runner must have all runs-on labels. Workflow: check and lighthouse on 'linux' (any runner), deploy-test and deploy-production on 'raspberry-pi' (deploys never on the PC; container actions do not work on Podman); deploy-test moved above lighthouse so a single free runner takes the deploy first while two runners run them in parallel. Commit/push and test runs allowed for this change."
**Context**: OPERATIONS - Deployment pipeline adjustment (during Monitoring Setup approval wait)
---