ci: use canonical penrose runner label - #2
Merged
jcrabtree merged 1 commit intoJul 24, 2026
Conversation
Route self-hosted jobs through the owner-scoped ARC scale set without encoding cluster placement in the GitHub runner label.
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
1 participant
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.
Why
Each GitHub organization has one canonical ARC label,
magnon-enterprise-runners-penrose. Cluster names are placement details and do not belongin GitHub's runner label. The bare shared label, ash/hel1/fsn1-prefixed labels, and
ifers-runnersare retired.What
Structurally migrates active workflow
runs-onselectors to exactlymagnon-enterprise-runners-penrose, preserving surrounding YAML comments and formatting.Test plan
magnon-enterprise-runners-penrose.