Skip to main content

RBE with GitHub Actions

Using BuildBuddy RBE with Github Actions is the simplest way to get started using BuildBuddy with a CI system.

Setup instructions#

There are three steps:

  1. Create a workflow file
  2. Update your .bazelrc
  3. Set up cert Github secrets

Workflow file#

All you have to do is create a file .github/workflows/main.yaml

name: CI
- master
runs-on: ubuntu-latest
- name: Checkout
uses: actions/checkout@v1
- name: Install bazelisk
run: |
curl -LO ""
mkdir -p "${GITHUB_WORKSPACE}/bin/"
mv bazelisk-linux-amd64 "${GITHUB_WORKSPACE}/bin/bazel"
chmod +x "${GITHUB_WORKSPACE}/bin/bazel"
- name: Create certs
run: |
echo "${{ secrets.BUILDBUDDY_ORG_CERT }}">buildbuddy-cert.pem
echo "${{ secrets.BUILDBUDDY_ORG_KEY }}">buildbuddy-key.pem
- name: Build
run: |
"${GITHUB_WORKSPACE}/bin/bazel" build --config=ci //...
- name: Test
run: |
"${GITHUB_WORKSPACE}/bin/bazel" test --config=ci //...

Updating your .bazelrc#

You'll then need to add the following configuration to your .bazelrc

build:ci --build_metadata=ROLE=CI
build:ci --build_metadata=VISIBILITY=PUBLIC
build:ci --tls_client_certificate=buildbuddy-cert.pem
build:ci --tls_client_key=buildbuddy-key.pem

Github secrets#

Finally, you'll need to create Github secrets with the contents of your buildbuddy-cert.pem and buildbuddy-key.pem files.

You can download these files by logging in to your BuildBuddy account and visiting your Setup instructions. You can then click Download buildbuddy-cert.pem and Download buildbuddy-key.pem.

You can then open these two files in a text editor, and add them as Github Secrets named BUILDBUDDY_ORG_CERT and BUILDBUDDY_ORG_KEY. For more information on setting up Github Secrets, click here.

Github commit statuses#

If you'd like BuildBuddy to publish commit statuses to your repo, you can do so by logging in and clicking Link Github Account in the user menu in the top right.


By default, authenticated builds are only visible to members of your BuildBuddy organization. If you'd like your BuildBuddy results pages to be visible to members outside of your organization, you can add the following line to your .bazelrc:

build:ci --build_metadata=VISIBILITY=PUBLIC

Remote build execution#

If you'd like to use BuildBuddy's Remote Build Execution capabilities in your CI workflow, you can add the following lines to your .bazelrc:

build:remote --bes_results_url=
build:remote --bes_backend=grpcs://
build:remote --remote_cache=grpcs://
build:remote --remote_executor=grpcs://
build:remote --remote_upload_local_results
build:remote --host_platform=@buildbuddy_toolchain//:platform
build:remote --platforms=@buildbuddy_toolchain//:platform
build:remote --crosstool_top=@buildbuddy_toolchain//:toolchain
build:remote --jobs=100
build:ci --config=remote

And the following lines to your WORKSPACE file:

name = "io_buildbuddy_buildbuddy_toolchain",
sha256 = "a2a5cccec251211e2221b1587af2ce43c36d32a42f5d881737db3b546a536510",
strip_prefix = "buildbuddy-toolchain-829c8a574f706de5c96c54ca310f139f4acda7dd",
urls = [""],
load("@io_buildbuddy_buildbuddy_toolchain//:deps.bzl", "buildbuddy_deps")
load("@io_buildbuddy_buildbuddy_toolchain//:rules.bzl", "buildbuddy")
buildbuddy(name = "buildbuddy_toolchain")

If you're using Java, or have a complex project - you'll likely need to configure the toolchain flags a bit. For more information, see our Remote Build Execution guide.