Repository navigation
rust-cache: cache-registry follows the crates mirror - #81
Merged
Merged
Conversation
A host that mirrors crates.io serves the index and the tarballs at LAN speed, so the registry archive only transfers bytes the mirror already holds. The new input takes "true", "false" or "auto"; auto skips the entry, restore and save alike, when RUST_CI_CRATES_MIRROR is set in the job environment, the same rule every auto follows. The registry-cached output and a cache.registry note say what happened; the selftest asserts both sides.
gronke
changed the title
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.
A self-hosted runner that hands
RUST_CI_CRATES_MIRRORto the job (docs/self-hosted.md) serves the crates.io index and the tarballs throughcrates-mirror, so the registry archive ofrust-cacheonly transfers bytes the mirror already holds.