Skip to content

ci: select runners by capability, not by location - #242

Merged
thedancingdeveloper merged 1 commit into
mainfrom
ci/drop-location-labels
Aug 19, 2026
Merged

ci: select runners by capability, not by location#242
thedancingdeveloper merged 1 commit into
mainfrom
ci/drop-location-labels

Conversation

@thedancingdeveloper

Copy link
Copy Markdown
Contributor

Drops node-b/linux/x64 from runs-on; keeps docker/publish/tailnet. Part of the 2026-08-19 development-cycle review — node-b was a location used as a fleet selector, leaving 2 of 5 runners idle while jobs queued at p90 207s. Every job audited for Docker use first. Policy gate unaffected (still requires literal self-hosted).

`runs-on` named `node-b`, `linux` and `x64`. The last two are advertised by
every self-hosted runner and selected nothing. `node-b` is a *location*, and
using it as a fleet selector is why proxmox-gha-public-rust and
wsl2-gha-public-rust sat idle — both `busy: false` — while all three Node B
workers were busy and jobs queued behind them at a p90 of 207s and a p99 of
1153s (2026-08-19 development-cycle review).

Labels now name capabilities only. Jobs that need a Docker daemon keep
`docker`/`publish`, which only the DinD-backed workers advertise; jobs needing
Tailnet reachability keep `tailnet`. Every job in this repository was checked
for Docker use before its label was dropped.

The org policy gate is unaffected: it requires the literal `self-hosted` and
rejects dynamic `runs-on`, both of which still hold.
@thedancingdeveloper
thedancingdeveloper merged commit 7395707 into main Aug 19, 2026
3 checks passed
@thedancingdeveloper
thedancingdeveloper deleted the ci/drop-location-labels branch August 19, 2026 04:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant