Google Git
Sign in
android / platform / prebuilts / bazel / common / refs/heads/gki13-boot-release
commit5a2cfa10f6f6b271e828aadfeaf1c5b4089dcb24[log] [tgz]
authorAndroid Build Coastguard Worker <android-build-coastguard-worker@google.com>Fri Oct 21 07:56:52 2022 +0000
committerAndroid Build Coastguard Worker <android-build-coastguard-worker@google.com>Fri Oct 21 07:56:52 2022 +0000
treec8edbf90936d2b9df158f73ec8c93d9224cc1f1a
parent181201de7288a974a9c3f08b3009f97e3125ab33 [diff]
parent42b5375fff69c30aa6ae8349c5d7177aed703587 [diff]
Snap for 9203002 from 42b5375fff69c30aa6ae8349c5d7177aed703587 to gki13-boot-release

Change-Id: I9bddac6cf1520eb7803f03504bf5a5bea494ae94
tree: c8edbf90936d2b9df158f73ec8c93d9224cc1f1a
  1. proto/
  2. remote_java_tools/
  3. bazel-complete.bash
  4. LICENSE
  5. README.md
  6. release_bazel.py
  7. update.sh
  8. update_tools.sh
README.md

Updating the Bazel prebuilts in AOSP

Instructions

First, decide which version of Bazel you need.

  • A Bazel release (e.g. Bazel 3.7.0)
  • A Bazel nightly
  • A Bazel per-commit build

Whichever of these you use, you will need to use official nojdk x86-64 versions of Bazel, for Linux and macOS (Darwin).

Run the update.sh script in the Linux prebuilts repository to download the and verify the binaries from the trusted Bazel CI pipeline:

./update.sh <commit>

To get the commit hash for builds, see the [Bazel releases], [Bazel nightlies] or [Bazel per-commit builds] sections below.

update.sh will also:

  • Download the remote_java_tools prebuilts corresponding to the downloaded Bazel binary
  • verify that the downloaded binary has the correct SHA-256 checksum as provided from Bazel CI metadata.

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:

  • For release builds only: Verifying the file signature, e.g.
  • Verifying that Bazel starts, on Linux and on macOS, e.g.
    • source build/envsetup.sh
    • bazel info
  • Verifying basic user journeys succeed.
    • ./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.

Obtaining Bazel binaries

The 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.

Bazel releases

The commit hash for linux and darwin nojdk x86-64 binaries are available from https://github.com/bazelbuild/bazel/releases

Bazel nightlies

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

Bazel per-commit builds

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: