Open
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
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 pull request enhances the Bazel CI workflow by integrating support for remote caching and Build Event Service (BES) endpoints, improving build performance and observability. Key changes include updating the Bazel setup GitHub Action to accept new remote cache and BES configuration inputs, adjusting cache usage to avoid pollution on pull requests, and propagating the relevant secrets and configuration through the CI workflow jobs.
Bazel Remote Cache & BES Integration:
.github/actions/setup-bazel/action.ymlfor remote cache endpoints, authentication headers, upload control, and BES endpoints. These inputs allow the action to be configured for remote caching and build event streaming.bazelrcsection. [1] [2]CI Workflow Configuration:
.github/workflows/ci.yml, sourcing secrets for endpoints and authentication headers, and conditionally enabling remote cache uploads only for non-pull request events to prevent cache pollution. [1] [2] [3]