Skip to content

ci: place every job through the shared router - #14

Open
bitcoinuniverseadmin wants to merge 3 commits into
mainfrom
ci/warpbuild-router-20260902
Open

ci: place every job through the shared router#14
bitcoinuniverseadmin wants to merge 3 commits into
mainfrom
ci/warpbuild-router-20260902

Conversation

@bitcoinuniverseadmin

Copy link
Copy Markdown
Collaborator

These workflows addressed RunsOn EC2 Spot directly, so they bypassed the capacity router entirely and pinned this repository 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

These workflows addressed RunsOn EC2 Spot directly, so they bypassed the
capacity router entirely and pinned this repository 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 and others added 2 commits September 2, 2026 05:50
GitHub does not expose private reusable workflows to public callers, so
the cross-repo reference to .github-private failed at startup. The
vendored adapter fetches the pinned router files at runtime.
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