Note: This document describes how to release java_tools for a JDK version that is already tested by Bazel. This document is addressed to trusted members of the Bazel team who have access to the Buildkite Bazel trusted pipelines and GCP. If you want to release the Java tools but don’t have these permissions please contact someone from the Bazel EngProd team (firstname.lastname@example.org).
The steps below are only meant to be followed as presented in order to release a new java_tools version. To understand the mechanism behind these steps and for more details about how the process works, see Behind the java_tools release process.
releaselabel. See #7 as an example.
java_tools binaries pipeline.
COMMIT_HASHthe commit hash where the pipeline was run (see below)
JDK_VERSIONthe JDK version for which you want to release
NEW_VERSIONthe new version number you’re trying to release (e.g.
RCthe number of the current release candidate
Create a new release candidate by running the command below from the bazel repo:
src/create_java_tools_release.sh \ --commit_hash $COMMIT_HASH \ --java_tools_version $NEW_VERSION \ --java_version $JDK_VERSION \ --rc $RC --release false
The script will output the sha256sum of the rc artifacts for linux, darwin and windows.
Create a new bazel Pull Request that updates the
html_archives with the new release candidates. See #8302 as an example. The PR triggers the CI presubmit.
src/create_java_tools_release.sh \ --java_tools_version $NEW_VERSION \ --java_version $JDK_VERSION \ --rc $RC --release true
http_archives in the upgrade PR and send it for review.
java_toolsbuilt at head.