| commit | a6d49fb35103e499a4b76d95b53e1caa6e704a5c | [log] [tgz] |
|---|---|---|
| author | Prakash Aswal <paswal@codeaurora.org> | Thu Feb 27 15:09:30 2020 +0530 |
| committer | Prakash Aswal <paswal@codeaurora.org> | Tue Mar 03 18:09:15 2020 +0530 |
| tree | a183420b23f86cad0b567c4f1134073ae96f8015 | |
| parent | 7cd28129ccb9e1edaf6e9b8d019be19e66698952 [diff] |
Enable aliases for change query has operands
Site administrators can alias 'has' operands from a plugin using the
'has-operand-alias' section and 'change' subsection in gerrit.config
[has-operand-alias change]
oldtopic = topic
Aliases are already supported for SSH commands [1], URLs [2] and
Operators [3]
This feature is particularly useful to alias 'has' operands (which may
be long and clunky as they include a plugin name in them) to shorter
operands without the plugin name. Admins should take care to choose
shorter operands that are unique and unlikely to conflict in the future.
Aliases are resolved dynamically at invocation time to the currently
loaded version of plugins. If a referenced plugin is not loaded, or does
not define the command, "unsupported operand" is returned to the user.
Aliases will override existing 'has' operands. In case of multiple
aliases with same name, the last one defined will be used.
When the target of an alias does not exist, the 'has' operand with the
name of the alias will be used (if present). This enables an admin to
configure the system to override a core 'has' operand with an operand
provided by a plugin when present and otherwise fall back to the 'has'
operand 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
[3]
https://gerrit-review.googlesource.com/Documentation/config-gerrit.html#operator-alias
Change-Id: Ifbd4f05079d8bf5eadd497d8e16e0bff203e6021
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.