commit | 61e7176bf0defc2d39c48ab665854442df1e18c5 | [log] [tgz] |
---|---|---|
author | Edwin Kempin <ekempin@google.com> | Tue Jun 27 09:56:38 2017 +0200 |
committer | Edwin Kempin <ekempin@google.com> | Tue Jun 27 13:10:03 2017 +0200 |
tree | fd44de0cfdc0d6465f3166361d5e2e9980441618 | |
parent | e53404645c32e0b5d18d1dfcfb9ac4a6b6a6d35e [diff] |
Do not require 'Create Reference' for pushing annotated tag Change I80ad478522 added an unconditional check for the 'Create Reference' permission in ReceiveCommands#parseCreate(...). Checking this permission on push of annotated tags is wrong as pushing annotated tags (for commits that already exist in the Gerrit repository) should (only) require the 'Create Annotated Tag' permission. The correct permission checks for pushing new branches and tags are implemented in RefControl#canCreate(...) and this method is also invoked from ReceiveCommands#parseCreate(...). This means we can simply drop the check for the 'Create Reference' permission in ReceiveCommands#parseCreate(...) as RefControl#canCreate(...) will check for this permission too, if it's needed (for pushing new branches and lightweight tags). This problem was not discovered by the PushTagIT because tests for pushing lightweight and annotated tags were executed in a loop. For testing pushing of lightweight tags the 'Create Reference' permission was assigned and it was still there when pushing of annotated tags was tested. To fix this PushTagIT is split into 2 tests, PushAnnotatedTagIT and PushLightweightTagIT. Change-Id: I656febfb71e9fb7d1e805c1a63ca9c32405b57e6 Signed-off-by: Edwin Kempin <ekempin@google.com>
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 Bazel and run the following:
git clone --recursive 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.