-
Notifications
You must be signed in to change notification settings - Fork 16k
Add remote caching to bazel builds #10767
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
mkruskal-google
merged 13 commits into
protocolbuffers:main
from
mkruskal-google:bazel-caching
Oct 18, 2022
Merged
Add remote caching to bazel builds #10767
mkruskal-google
merged 13 commits into
protocolbuffers:main
from
mkruskal-google:bazel-caching
Oct 18, 2022
Conversation
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
devjgm
approved these changes
Oct 12, 2022
38de232 to
4faf023
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.
This enables remote caching for all of our Bazel builds. This will have the largest impact on reruns, but should hopefully speed up all our CI builds.
Note: each job is given its own cache to avoid issues from non-hermetic builds. For example, if the version of python changes our current setup doesn't give Bazel enough knowledge to know the cache is stale. Ruby, PHP, C#, and Objective-c likely have this issue as well, since they all use non-hermetic genrules to grab system dependencies. Once all of these have been fully modified we can likely fall back to a single shared cache