Go to file
Edwin Kempin 14e65d16dc RetryHelper: Let callers care about exception handling
When retrying actions it is specific to the caller which exceptions
should be rethrown and which exceptions should be wrapped. At the moment
RetryHelper has 2 kinds of execute methods that are suitable for change
updates and account updates. These execute methods do not fit for all
cases, e.g. ReceiveCommits uses RetryHelper to retry change queries, but
the execute method requires handling of ConfigInvalidException which
cannot occur during index queries.

Instead of adding more specific execute methods to RetryHelper, just let
the execute method throw Exception and let the caller take care about
the exception handling. The execute method that is specific for change
updates is kept in RetryHelper because it has many callers. All other
exception handling is currently unique for one caller, hence it's not
needed to keep a specialized execute method for these cases in
RetryHelper. We can add more specifc execute methods to RetryHelper once
the same exception handling is required by multiple callers to share
the exception handling code.

Change-Id: I7cf2b92fb228d2d6dddd89df5c338e53a2f8f526
Signed-off-by: Edwin Kempin <ekempin@google.com>
2018-01-22 14:17:23 +01:00
2017-12-20 08:16:51 +09:00
2017-11-02 08:54:01 -04:00
2018-01-09 16:57:11 -08:00
2018-01-19 15:05:24 +01:00
2018-01-08 13:50:31 +00:00
2017-11-17 10:39:19 -08:00
2017-07-19 15:32:39 +09:00
2008-11-14 16:59:34 -08:00
2009-03-27 20:20:10 -07:00
2018-01-16 08:32:00 +01: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