ci: migrate runner selectors off retired node-b/rust labels - #13
Merged
Merged
Conversation
Completes the 2026-08-19 runner-label convention ("labels are
capabilities, not locations; rust is a fiction"):
[self-hosted, node-b, linux, x64, rust] -> [self-hosted]
[self-hosted, linux, x64, rust] -> [self-hosted]
[self-hosted, node-b, linux, x64, publish, docker] -> [self-hosted, docker, publish]
The node-b location gate and the rust fiction restricted rust jobs to
the 3 node-b runners while 3 capable node-f runners sat idle. Bare
[self-hosted] still matches every existing runner (all carry the
self-hosted/Linux/X64 defaults), so this only widens the pool.
Container jobs keep their real docker/publish capabilities.
Fleet-wide migration (Vogt WI-25). Canaried on rustnzb#120: rust/
frontend jobs verified running and passing on node-f runners.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DjwX7G4UVdpDpVo4bkpGvi
thedancingdeveloper
force-pushed
the
chore/runner-labels-convention
branch
from
September 7, 2026 01:37
64982bc to
4853eb6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Completes the 2026-08-19 runner-label convention (labels are capabilities, not locations;
rustis a fiction):[self-hosted, node-b, linux, x64, rust]/[self-hosted, linux, x64, rust][self-hosted][self-hosted, node-b, linux, x64, publish, docker][self-hosted, docker, publish]Why
The
node-blocation gate + therustfiction pinned rust jobs to the 3 node-b runners while 3 capable node-f runners sat idle. Every runner already carries the defaultself-hosted/Linux/X64labels, so bare[self-hosted]matches the same runners plus node-f/proxmox — only widening the pool. Container jobs keep their realdocker/publishcapabilities.Provenance
Fleet-wide migration, Vogt WI-25. Canaried on TheDancingDeveloper-org/rustnzb#120, where the
rustandfrontendjobs were verified running and passing on node-f runners (nodef-gha-public-rust,nodef-gha-public-rust-3).🤖 Generated with Claude Code
https://claude.ai/code/session_01MBbSsMNo6TQEcPRo6MHHUP