Repository navigation
ci: save Rust caches only on pushes, and let releases read CI's image caches - #87
Merged
Merged
Conversation
… caches - ci.yml: `rust-cache` saves only on pushes to dev and main. A PR can read its own caches, its base branch's and the default branch's, never another PR's, so a cache saved on a PR served only a later push to that same PR while taking as much of the 10 GB quota as dev's (refs/pull/85/merge held 2.2 GB). - release.yml: image builds read the caches CI saves on main and write none. The release scopes (`server-linux-amd64`, `web-linux-amd64`, ...) never matched CI's (`server-linux/amd64`, `web`), and a tag run can read only its own caches and main's, so every release built the images from scratch and filed caches under the tag that no later run could read. The tag points at a main commit CI has just built from the same Dockerfiles. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
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.
rust-cachesaves only on pushes to dev and main. A PR can read itsown caches, its base branch's and the default branch's, never another PR's,
so a cache saved on a PR served only a later push to that same PR while
taking as much of the 10 GB quota as dev's (refs/pull/85/merge held 2.2 GB).
The release scopes (
server-linux-amd64,web-linux-amd64, ...) nevermatched CI's (
server-linux/amd64,web), and a tag run can read only itsown caches and main's, so every release built the images from scratch and
filed caches under the tag that no later run could read. The tag points at
a main commit CI has just built from the same Dockerfiles.
🤖 Generated with Claude Code