commit | 70a16104e386c26b69c4db1fe575ce5016c1396c | [log] [tgz] |
---|---|---|
author | Zac Livingston <zacl@codeaurora.org> | Tue Nov 20 15:07:34 2018 -0700 |
committer | Nasser Grainawi <nasser@codeaurora.org> | Tue Oct 22 12:35:39 2019 -0600 |
tree | 4dfe4b69ff9373f2071ba05101957cf5bc4b56eb | |
parent | 547b1108063e5411b0c3f97eb94b4f77bc4d88c5 [diff] |
Enable aliases for change query operators Site administrators can alias change query operators from a plugin using the 'operator-alias' section and 'change' subsection in gerrit.config: [operator-alias "change"] oldage = age number = change Aliases are already supported for SSH commands [1] and URLs [2]. This feature is particularly useful to alias operator names which may be long and clunky because they include a plugin name in them to a shorter name without the plugin name. Admins should take care to pick short names that are unique and unlikely to be used by future operators. Aliases are resolved dynamically at invocation time to any currently loaded versions of plugins. If the alias points to an operator provided by a plugin which is not currently loaded, or the plugin does not define the operator, then "unsupported operator" is returned to the user. Aliases will override existing operators. In the case of multiple aliases with the same name, the last one defined will be used. When the target of an alias doesn't exist, the operator with the name of the alias will be used (if present). This enables an admin to config the system to override a core operator with an operator provided by a plugin when present and otherwise fall back to the operator provided by core. The above three features can make aliases useful for cases of moving functionality from Gerrit core to plugins and vice versa. [1] https://gerrit-review.googlesource.com/Documentation/config-gerrit.html#ssh-alias [2] https://gerrit-review.googlesource.com/Documentation/config-gerrit.html#urlAlias Change-Id: I3c60b0b9bc84467fece4b7d30dc735509e28071d
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 7 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]
To run a Ubuntu 15.04 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.