ci: scope the GHA docker layer caches so the two images stop evicting each other - #430
Merged
Conversation
… each other publish-image.yml (the Rust gateway) and explore.yml (the Flutter SPA) both used a bare `cache-from/to: type=gha`. A bare type=gha is a single shared scope, so two entirely unrelated images were writing over each other's layer cache — whichever built last left the other cold. Distinct scopes give each image its own. Matches triton, which already scopes per image (scope=dz-triton). Co-Authored-By: Claude Opus 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.
Part of harmonizing CI across escurel / peacock / triton / agent-template.
publish-image.yml(the Rust gateway image) andexplore.yml(the Flutter SPA image) both used a bare:A bare
type=ghais a single shared scope. Two entirely unrelated images were writing over each other's layer cache, so whichever built last left the other cold. Neither workflow was getting the cache it thought it had.Distinct scopes (
escurel-server,escurel-explore) give each image its own. triton already does this (scope=dz-triton); escurel was the outlier.Test plan
Both workflows are main/tag-triggered and path-filtered, so a PR cannot exercise them — like any cache change, the first run after this is cold by definition and the second is the one that shows the benefit. The change is two lines per workflow and reversible.
Verified locally: both files still parse (
yaml.safe_load), and the surroundingbuild-push-actioninputs are otherwise untouched.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.