ci: place every job through the shared router - #15
Merged
bitcoinuniverseadmin merged 1 commit intoSep 2, 2026
Merged
Conversation
These workflows addressed RunsOn EC2 Spot directly, so they bypassed the capacity router entirely and pinned this branch to a cloud provider that is being retired. Each job now calls the shared router in .github-private, which prefers idle permanent self-hosted capacity and spills to cloud overflow only when the local fleet is busy. Runner classes were derived from the vCPU band each job already asked for, then raised where the job body shows it needs Docker or a browser, and deployment jobs that hold production credentials were pinned to the local fleet so a reclaimed cloud instance cannot interrupt a cutover. No step logic changed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
bitcoinuniverseadmin
deleted the
ci/warpbuild-router-develop-20260902
branch
September 2, 2026 05:30
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.
These workflows addressed RunsOn EC2 Spot directly on
develop, so they bypassed the capacity router entirely and pinned this branch to a cloud provider that is being retired.Each job now calls the shared router in
.github-private, which prefers idle permanent self-hosted capacity and spills to cloud overflow only when the local fleet is busy.Runner classes were derived from the vCPU band each job already asked for, then raised where the job body shows it needs Docker or a browser. Deployment jobs that hold production credentials are pinned to the local fleet so a reclaimed cloud instance cannot interrupt a cutover.
No step logic changed.
🤖 Generated with Claude Code