Use cargo-chef so the Docker layer cache works - #1
Merged
Merged
Conversation
cache-to: type=gha exports image layers only: the contents of RUN cache mounts (cargo registry, target/) live inside the buildx builder, which CI recreates on every run. The COPY . . layer changes with every commit, so the cargo build layer never hits and each push compiles all dependencies from scratch (~10 min). cargo-chef moves dependency compilation into a layer keyed only by recipe.json, derived from Cargo.toml/Cargo.lock. That layer survives source-only commits, so a typical build recompiles just this crate.
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.
cache-to: type=gha exports image layers only: the contents of RUN cache mounts (cargo registry, target/) live inside the buildx builder, which CI recreates on every run. The COPY . . layer changes with every commit, so the cargo build layer never hits and each push compiles all dependencies from scratch (~10 min).
cargo-chef moves dependency compilation into a layer keyed only by recipe.json, derived from Cargo.toml/Cargo.lock. That layer survives source-only commits, so a typical build recompiles just this crate.