commit | 7032f992c3dab3bbec0d31febd760b5f306bed2a | [log] [tgz] |
---|---|---|
author | Youssef Elghareeb <ghareeb@google.com> | Wed Jan 19 15:48:48 2022 +0100 |
committer | Youssef Elghareeb <ghareeb@google.com> | Wed Jan 19 17:39:29 2022 +0100 |
tree | 1a7416041b99a5208c0056dad8965849ca5dcde2 | |
parent | 7398fcd40b4bdbba772ab0371d8a312b8c920bd4 [diff] |
Adapt submit requirements names created of plugins' legacy submit rules We create submit requirement results out of legacy submit records. This included the evaluation of the default, custom and prolog submit rules and converting the resulting submit records into submit requirements. For submit records that have one or more labels, we created a separate submit requirement result for each label. However if the record contained no labels, we named the submit requirement after the plugin name and the implementing class name like: $pluginName~$implementingClass For example, for the code-owners plugin, the corresponding submit requirement name was created as "code-owners~CodeOwnerSubmitRule" which is not a user friendly name. In this change we adapt SubmitRuleEvaluator not to backfill SubmitRecord#ruleName if it was populated by the plugin. We also added changes to the code-owners and simple-submit-rules plugins to export the ruleName with the returned submit records. Google-Bug-Id: b/211464678 Change-Id: I336c7de83b251cdaef84341a23ab105bff9f39a1
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.