fix(ci): switch from GHA cache to registry cache#12
Merged
Conversation
The 10GB GitHub Actions cache limit was exceeded with 14 parallel builds (7 services × 2 platforms), causing cache eviction thrashing where new cache entries would evict old ones before they could be used. Switch to registry cache which stores the build cache as tags in ghcr.io (e.g., image:cache-amd64). This has no practical size limit and avoids the eviction problem entirely.
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
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.
Summary
Switch from GitHub Actions cache to registry cache to fix build caching.
Root Cause
The previous caching attempts failed because:
power-service-amd64cache index was being evicted almost immediately after creationSolution
Use registry cache instead of GHA cache:
image:cache-amd64)Changes