Han-Wen Nienhuys 4e8a19ccf9 Push ReceiveError advice into structured exception type
The ReceiveCommits.ReceiveError is very specific to the
DefaultPermissionBackend. Provide a way for other backend
implementations to provide their own advice, by enriching the
AuthException hierarchy.

We now have a PermissionDeniedException which records up to three items:
 * The description of the permission, as returned by
   GerritPermission#describeForException.
 * Free-form advice for addressing the issue.
 * The resource name, if applicable.

Now, ReceiveCommits doesn't have to know about the ReceiveError text;
DefaultPermissionBackend can just set the advice on any AuthExceptions
it throws. Currently, the advice is only displayed over the wire during
ReceiveCommits, but one could imagine that it might be helpful in bare
HTTP responses as well, for example.

Update the push permissions test to account for the new messages. Note
that they are much more consistent and follow a common format, which is
not surprising since a goal of this change was to eliminate much of the
hard-coding in ReceiveCommits.

There are a few tests in PushPermisisonsIT which still show hard-coded
error messages. These will require a bit more work to make sure they get
understandable messages and advice.

Change-Id: I34dc173ffd040829d8ff2853d4a728fa323137b5
2018-08-16 14:07:48 +02:00
2018-02-12 11:11:53 +01:00
2018-07-19 11:23:15 +09:00
2018-08-07 08:51:12 -07:00
2018-08-10 15:55:52 +01:00
2018-04-18 08:52:53 +02:00
2018-06-25 07:32:47 +02:00
2008-11-14 16:59:34 -08:00
2009-03-27 20:20:10 -07:00
2018-06-15 10:27:42 +00:00
2018-07-31 14:20:18 +02:00

Gerrit Code Review

Gerrit is a code review and project management tool for Git based projects.

Build Status

Objective

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.

Documentation

For information about how to install and use Gerrit, refer to the documentation.

Source

Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.

Reporting bugs

Please report bugs on the issue tracker.

Contribute

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.

Getting in contact

The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.

The Developer Mailing list is repo-discuss on Google Groups.

License

Gerrit is provided under the Apache License 2.0.

Build

Install Bazel and run the following:

    git clone --recursive https://gerrit.googlesource.com/gerrit
    cd gerrit && bazel build release

Install binary packages (Deb/Rpm)

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>]

Use pre-built Gerrit images on Docker

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.

Description
RETIRED, Gerrit as used by OpenStack
Readme 120 MiB