| commit | e5a9d01abbdb06e03504a77de624b67939c67a70 | [log] [tgz] |
|---|---|---|
| author | Janice Agustin <janice.agustin@ericsson.com> | Mon Aug 24 09:05:56 2015 -0400 |
| committer | Marco Miller <marco.miller@ericsson.com> | Wed Sep 09 13:27:47 2015 -0400 |
| tree | 8cb8cc7710174f9d58464ad7e775aac386b0f5ef | |
| parent | 1912561ec1194b34317e4044b259af48eb2f623c [diff] |
Allow plugins to reference groups in project config Groups should be recognized in the plugin section of project configuration. They shall be referenced as a string containing both the group name and uuid. The format to use shall be "Group[name / uuid]", which is the string representation of a GroupReference. Using this format will allow groups referenced in plugin configs to be updated when a group is renamed. It will also validate that the group exists in the groups file. This format does not follow the standard "name = group group_name". Project config must know about both the group name and uuid in order to update the name and reload the config without errors. To rename a group, the groups file [1] for each project is parsed for the uuid. If it is found, the name is updated in the file. Groups are loaded by getting the list of GroupReferences for a section and grabbing the name from the file by uuid. Utilizing GroupReferences allows project config to display the group name without the uuid. However, plugin config entries do not support GroupReferences. This is why the string representation of this object is used. [1] Documentation/config-project-config.html#file-groups Change-Id: I1160f1f55df07243faf0034989ecbbd02a9ca19c
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 IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Buck and run the following:
git clone --recursive https://gerrit.googlesource.com/gerrit
cd gerrit && buck build all
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>]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.