docs(ci): record why image builds stay on GitHub-hosted runners - #846
Open
funkypenguin wants to merge 1 commit into
Open
docs(ci): record why image builds stay on GitHub-hosted runners#846funkypenguin wants to merge 1 commit into
funkypenguin wants to merge 1 commit into
Conversation
The 2026-08-23 org billing failure prompted an org-wide move of release-blocking workflows to the in-cluster arc-runners pool. This repo's image builds are release-blocking, so the absence of a change here needs to be a recorded decision rather than an oversight -- particularly since the obvious next step for a future reader is a blanket runs-on swap that would break every build. Comment only -- no behaviour change. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Comment-only. Closes the "decide on the containers build workflows" item from
docs/BRIEF-arc-runners-release-workflows.md(elfhosted/shadowfax#561), which called this the heavyweight case and asked for a deliberate decision rather than a silent deferral.The decision is: don't move them — and the reason is not the one the brief expected.
ubuntu-latestjob in the org's private repos died in 4–5s for ~15h from 13:11Z, this repo's jobs ran clean — Release: Manual at 21:03Z and 01:44Z, Image: Rebuild at 01:55Z, and hourly Renovate throughout.containerMode, so runner pods have no Docker daemon (buildx is a non-starter) and no sudo/apt (generate-build-matrixinstallsmoreutilsandjo).The comment goes in
release-manual.yamlbecause that's where the next person will ask the question, and because the obvious-looking fix (a blanketruns-onswap) would break every build.Revisit if this repo ever goes private, or if public-repo minutes start being metered.
Also spotted while looking, not addressed here:
Release: Schedulehas been failing continuously — before, during and after the incident. Those runs last 300–750s and then fail, so that's real job logic failing, not a 4-second billing rejection. Wanted to flag it rather than fold it into a docs PR.Full inventory and rationale:
docs/DECISION-arc-runners-release-workflows.mdin elfhosted/shadowfax.