| commit | 21a891c7a1b766ddaf5a4d7cfb3eea3189292826 | [log] [tgz] |
|---|---|---|
| author | David Ostrovsky <david@ostrovsky.org> | Sat Dec 19 12:57:06 2020 +0100 |
| committer | David Ostrovsky <david@ostrovsky.org> | Tue Jan 25 07:33:52 2022 +0100 |
| tree | 046a162f03bc8d18350b15011e4d7c66f4285654 | |
| parent | 40a0e680422db01797025c0cc3409cff21313b53 [diff] |
Bazel: Switch to using toolchain resolution for java rules Bump Bazel version to release 5.0.0. In this new Bazel release, --incompatible_use_toolchain_resolution_for_java_rules is flipped, that means that the build must be adapted to toolchain resolution. Specification toolchain resolution for java rules is here: [1]. Main tracking Bazel issue is here: [2]. Given that new Bazel release also added support for remote JDK 17, add support for building with remote JDK 17 to produce major byte code version 61. Note that some tests are still failing on JDK 17. This will be fixed in follow-up change. This change has a number of side effects: o Remove workaround for Bazel worker multiplexer bug, see: [3]. o Demote severity for EP bug patterns from error to warning: - DoNotMockAutoValue o Re-enable EP bug pattern: - FutureReturnValueIgnored Test Plan: To build with JDK 11 run: $ bazel build release To build with JDK 17 run: $ bazel build --config java17 release To build with JDK 11 on RBE run: $ bazel build --config=remote --remote_instance_name=<name> release To build with JDK 17 on RBE run: $ bazel build --config=remote17 --remote_instance_name=<name> release [1] https://docs.google.com/document/d/1MVbBxbKVKRJJY7DnkptHpvz7ROhyAYy4a-TZ-n7Q0r4/edit?usp=sharing [2] https://github.com/bazelbuild/bazel/issues/7849 [3] https://github.com/bazelbuild/bazel/issues/13333 Change-Id: Ib3b923db7bb97a24d52ae8468ad1532a970203b5
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
cd gerrit && bazel build release
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update & apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
On Fedora run:
dnf clean all && dnf install gerrit-<version>[-<release>]
Docker images of Gerrit are available on DockerHub
To run a CentOS 8 based Gerrit image:
docker run -p 8080:8080 gerritcodereview/gerrit[:version]-centos8
To run a Ubuntu 20.04 based Gerrit image:
docker run -p 8080:8080 gerritcodereview/gerrit[:version]-ubuntu20
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.