ci: stop fork build from writing gha cache#93
Merged
Conversation
The repo GHA cache sits at ~9.3 GB against the 10 GB per-repo limit (filled by docker-publish's mode=max export), so the fork build's own cache-to export could not reserve space and failed with: error writing layer blob: failed to reserve cache Fork builds are occasional test builds, so drop cache-to entirely and only read the publish scope's warm layers for speed. No new reservation, no quota growth. Assisted-by: ClaudeCode:claude-opus-4-8 Signed-off-by: skjnldsv <skjnldsv@protonmail.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.
What
Drop
cache-tofrom the fork build; keep a read-onlycache-fromon thepublishscope.Why
The fork build kept failing with:
Root cause is the repo GHA cache quota, not buildx or scopes. Usage sits at ~9.3 GB against GitHub's 10 GB per-repo limit (143 entries, all from
docker-publish'smode=maxexport). The fork build's ownmode=maxcache-tocan't reserve the space it needs, so the export fails.Fork builds are occasional, maintainer-gated test builds — they don't need to persist cache. Reading the already-warm
publishlayers keeps them reasonably fast without adding to the quota.Testing
sha-<commit>succeeds, no cache error.AI-assisted change.