| commit | 2f23187b8db361448b98a65e4821df1f3d41d8eb | [log] [tgz] |
|---|---|---|
| author | David Ostrovsky <david@ostrovsky.org> | Tue Jan 11 21:51:15 2022 +0100 |
| committer | David Ostrovsky <david.ostrovsky@gmail.com> | Thu Jan 13 19:48:49 2022 +0000 |
| tree | c417d9541a367b0005ac13deddd6bd57fcf67655 | |
| parent | 6a6fcde8042b4e6e6f8ac9c8c4b452e49b45b71a [diff] |
Bazel: Use Java 8 per default to guarantee source level compatibility At the time the change 264535 was submitted, that switched Java default to Java 11, not all Gerrit users were ready to abandon Java 8 compatibility. To provide Java 8 compatibility it was decided to perform CI verification with Java 8, by overriding the java toolchain option on GerritForge CI (core build) and Zuul (plugins build). Today the situation is different. Starting from stable-3.5 branch Java 8 compatibility has been dropped. Still we guarantee the Java 8 compatibility on stable-3.3 and stable-3.4 branches. To achieve this, the java toolchain option is overridden on stable-3.3 and stable-3.4 branches on the CI. To simplify the build toolchain and the CI configurations, we would like to rely only on the default java toolchain (provided in .bazelrc) to be the minimum guaranteed compatible Java version (on each branch). That way the default bazel invocation: $ bazel build :release would always provide the desired result per default. This change should be reverted when merged up to stable-3.5 branch. To summarize: before this change is submitted, the situation is: stable-3.3: default toolchain: Java 11, guaranteed compatibility: Java 8 stable-3.4: default toolchain: Java 11, guaranteed compatibility: Java 8 from stable-3.5: default toolchain/guaranteed compatibility: Java 11 after this change is submitted, merged to stable-3.4 branch and reverted started from stable-3.5 branch, the situation is: stable-3.3: default toolchain/guaranteed compatibility: Java 8 stable-3.4: default toolchain/guaranteed compatibility: Java 8 from stable-3.5: default toolchain/guaranteed compatibility: Java 11 Change-Id: Ieb0d627ce5f4d2753fe637fb67123e6431796940
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.