Cache: Add support for explicitly choosing compression, and zero compression #1877
+316
−31
Conversation
This file contains 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
16987814
approved these changes
Nov 25, 2024
planetmarshall
force-pushed
the
cache-custom-compression
branch
from
227eeec
to
e7ec923
Compare
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.
Objective
Allow explicit specification of compression type when caching, including none.
Motivation
Some third party tools (notably conan) provide their own caching mechanism that already produces compressed archives. To benefit from using Github's caching, it is more efficient to provide a way to upload these artifacts without compressing them a second time.