Enable buildbuddy in CI workflows build_and_test.yml and docs.yml#3104
Merged
Conversation
j2kun
force-pushed
the
buildbuddy-enable
branch
3 times, most recently
from
c8afc3b to
e79967d
Compare
asraa
approved these changes
Jun 23, 2026
| labels: ubuntu-24.04-64core | ||
| env: | ||
| BUILDBUDDY_API_KEY: ${{ github.event_name != 'pull_request' && secrets.BUILDBUDDY_API_KEY || vars.BUILDBUDDY_READ_ONLY_API_KEY }} | ||
| BUILDBUDDY_API_KEY: ${{ github.event_name != 'pull_request' && secrets.BUILDBUDDY_API_KEY || '7eYz4UY70YSrT55wmjWV' }} |
Collaborator
There was a problem hiding this comment.
wdyt about putting the read only key string directly into the .bazelrc for build:common or ci? that way we sync across all the workflows
Collaborator
Author
There was a problem hiding this comment.
I tried that, but then this env setting overrides it via the flag with an empty string.
| common --noremote_upload_local_results # Uploads logs & artifacts without writing to cache | ||
| common --remote_cache=grpcs://heir.buildbuddy.io | ||
| common --remote_cache_compression | ||
| common --remote_header=x-buildbuddy-api-key=IqGGzfrvMgDJh927qtrw |
Collaborator
There was a problem hiding this comment.
this one is different than the one in CI "7eYz4UY70YSrT55wmjWV"? could you add a comment for this (is this read-only as well? hopefully this isn't your personal one)
Collaborator
Author
There was a problem hiding this comment.
Indeed, two separate read-only keys. I wanted to make them different for metrics tracking purposes (if one key starts being abused, we can know where it's coming from).
j2kun
added
the
pull_ready
asraa
approved these changes
Jun 23, 2026
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
2 participants
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 change adds support for buildbuddy in the CI workflows.
However, due to GitHub's security isolation, we can't directly load the buildbuddy API key used for remote builds from a GH pull request. So we have a (public) read-only key that at least allows one to pull in cached build artifacts.
The configuration here also (hopefully) sets up the build_and_test workflow that runs on main to use RBE, which I can't test until this is merged. But once that workflow runs, then the Content addressable storage cache should reflect in faster pull_request builds with the read-only key.
https://heir.buildbuddy.io/invocation/4dd62bd8-bb88-4049-8f0a-2988d008d655
Includes instructions on using buildbuddy as a developer in the README.