commit | 9ced62c97c5944172c9a5d7a83312c11879beca7 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Dec 20 11:08:08 2021 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Dec 20 11:08:08 2021 +0000 |
tree | 2dd17ba331ee8206edad3370bc7d6bc3c7c36e4e | |
parent | 7f20b99e9f630a0da0c2238eca9040e6be4cd6ef [diff] | |
parent | 17dac6ab7069d14d80fe25649d69d0436ba9689b [diff] |
Snap for 8014993 from 17dac6ab7069d14d80fe25649d69d0436ba9689b to s-keystone-qcom-release Change-Id: I3d21e140c34212503e768c064c0d64c2891e4ad9
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).
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 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 two CLs, to update the Linux and macOS 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 the two CLs descriptions, 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
source build/envsetup.sh
bazel info
build/bazel/scripts/milestone-2/demo.sh full
build/bazel/scripts/milestone-2/demo.sh generate && build/bazel/scripts/milestone-2/demo.sh sync && USE_BAZEL=1 USE_BAZEL_ANALYSIS=1 m libc
Ensure that the Linux and Darwin CLs are set to the same Gerrit topic so they are submitted together.
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.
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:
https://storage.googleapis.com/bazel-builds/metadata/<commit>.json