tag | 49c2b4aed31fb19195f28822aaf4ab7b838cd591 | |
---|---|---|
tagger | Xin Li <delphij@google.com> | Wed Apr 24 20:18:41 2024 -0700 |
object | 321a057530dea4e6d210c8542ecf0909ff1177cb |
aml_odp_341610000 (11382236,com.google.android.go.ondevicepersonalization,com.google.android.ondevicepersonalization)
commit | 321a057530dea4e6d210c8542ecf0909ff1177cb | [log] [tgz] |
---|---|---|
author | Romain Jobredeaux <jobredeaux@google.com> | Thu Apr 13 23:06:47 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Apr 13 23:06:47 2023 +0000 |
tree | 47f427f139c82d7f175a32c4b5f696976b42e396 | |
parent | c3144ee4b2d2d16cf6b1654b97761a7f3777ed48 [diff] | |
parent | baa93d1c0b5f2ac6cf02ef9c41dd280ea0bafe35 [diff] |
Alias ijar_cc_binary and singlejar_cc_bin to prebuilts in java tools am: 133a600c82 am: 138067d91d am: 3789562e8f am: baa93d1c0b Original change: https://android-review.googlesource.com/c/platform/prebuilts/bazel/common/+/2532599 Change-Id: I064c7f7f40b5c6a267ce1974520944b005dcee85 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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:
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
source build/envsetup.sh
bazel info
./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.
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