First, decide which version of Bazel you need.
Whichever of these you use, you will need to use official nojdk x86-64 versions of Bazel, for Linux and macOS (Darwin).
update.sh script in the Linux prebuilts repository to download the and verify the binaries from the trusted Bazel CI pipeline:
To get the commit hash for builds, see the [Bazel releases], [Bazel nightlies] or [Bazel per-commit builds] sections below.
update.sh will also:
Once you have the binaries, you will need to create and send up to three CLs, to update the Linux, macOS, and platform-agnostic prebuilts that live in separate Git repositories, i.e.
The update script does not automatically create CLs, so you need to create them manually. In each CL description, mention the testing you did, which should at least include:
gpg --import bazel-release.pub.gpg
gpg --verify bazel_nojdk-<commit>-linux-x86_64.sig
./build/bazel/scripts/run_presubmits.sh(or let TreeHugger run these presubmits for you)
Ensure that the CLs are set to the same Gerrit topic so they are submitted together.
update.sh script automates downloading Bazel binaries. The next sections describe how the different Bazel binaries (release, nightly, per-commit) can be manually downloaded from the Bazel CI.
The commit hash for linux and darwin nojdk x86-64 binaries are available from https://github.com/bazelbuild/bazel/releases
The commit hash and urls for linux and macOS nojdk x86-64 binaries are available in https://storage.googleapis.com/bazel-builds/metadata/latest.json
You need to know the GitHub commit that contains your change, e.g. https://github.com/bazelbuild/bazel/commit/364a867df255c57c8edc4a8aae8f78cb54900a54
And the linux and macOS nojdk x86-64 binaries are available from: