Set up remote caching in CI (cherry-pick of #19144) #19163
Merged
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
Runs a sidecar bazel-remote server in a docker container. This server uses S3 as its storage backend, specifically a new cache.pantsbuild.org bucket. Read/write access requires our AWS secret key, which is not accessible to PRs across forks. So to write to this cache, a PR must be from a branch in the pantsbuild/pants repo. We can establish protocols by which a set of trusted contributors can push to feature branches in pantsbuild/pants and submit PRs from them, rather than from forks, to get the best CI speedups. PRs across forks can still read from the cache, via restricted creds.
huonw
approved these changes
May 26, 2023
Merged
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.
Runs a sidecar bazel-remote server in a docker container. This server uses S3 as its storage backend, specifically a new cache.pantsbuild.org bucket.
Read/write access requires our AWS secret key, which is not accessible to PRs across forks. So to write to this cache, a PR must be from a branch in the pantsbuild/pants repo.
We can establish protocols by which a set of trusted contributors can push to feature branches in pantsbuild/pants and submit PRs from them, rather than from forks, to get the best CI speedups.
PRs across forks can still read from the cache, via restricted creds.