Skip to content
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

build: Use bazel-remote for Bazel remote caching #1834

Closed
wants to merge 2 commits into from

Conversation

SanjayVas
Copy link
Member

@SanjayVas SanjayVas commented Sep 30, 2024

This should be more efficient as it uses gRPC over HTTP/2. It has the additional benefit that it does not depend on Google Cloud credentials, so it can be used in cases where different credentials are already in use (e.g. applying K8s configs).

@wfa-reviewable
Copy link

This change is Reviewable

@SanjayVas SanjayVas changed the base branch from sanjayvas-thread-pool-instrumentation to main September 30, 2024 21:12
@SanjayVas SanjayVas force-pushed the sanjayvas-bazel-remote branch 4 times, most recently from e2da701 to 89f878a Compare October 1, 2024 22:23
@SanjayVas SanjayVas force-pushed the sanjayvas-bazel-remote branch 3 times, most recently from 35317da to be0b232 Compare October 2, 2024 23:16
This should improve query performance and reduce test flakiness.
This should be more efficient as it uses gRPC over HTTP/2.
@SanjayVas SanjayVas force-pushed the sanjayvas-bazel-remote branch from be0b232 to ba039ef Compare October 3, 2024 17:28
@SanjayVas
Copy link
Member Author

Closing in favor of #1840

@SanjayVas SanjayVas closed this Oct 23, 2024
@SanjayVas SanjayVas deleted the sanjayvas-bazel-remote branch October 23, 2024 17:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants