ci: s3 cache - #1167
Merged
Merged
Conversation
This was referenced Jun 23, 2023
Closed
strophy
requested changes
Jul 6, 2023
strophy
left a comment
Collaborator
There was a problem hiding this comment.
This is looking really good! Let's make a few more changes for readability
5 tasks
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
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.
Issue being fixed or feature implemented
Self-hosted runners are expensive so we need to utilize cache as much as possible to reduce costs.
This PR is using s3 store as a cache backend for NPM, Cargo, Docker build and Rust build caches in CI
There is some work needed to support ARM builds in a proper way
What was done?
This PR contains prelumeary work from #1105 and #953
How Has This Been Tested?
Running CI and locally
Breaking Changes
None
Checklist:
For repository code-owners and collaborators only