Go to file
Dave Borowitz a11b59c424 Store push certificate in patch set during ReceiveCommits
Push certificates for new/updated changes contain commands for
refs/for/*, even though that ref is not created. This means if we
store such certificates in PushCertificateStore, we can't use the
history of push certs on that ref to reconstruct anything like a
reflog. It would be confusing to see in refs/meta/push-certs a push
cert mentioning refs/for/* either on that ref (which doesn't exist) or
refs/changes/* (which is a completely unrelated refname).

Pushing to refs/for/* and having the data become a patch set is a
detail of the Gerrit model, so it makes sense to store the cert in the
same place as the patch set SHA-1 itself, namely the PatchSets table.

Change-Id: I51924054742fbd31b1abcce1ccdcf9bce76642ac
2015-10-09 10:04:18 -04:00
2015-10-09 22:06:39 +09:00
2015-10-09 16:07:35 +09:00
2015-08-21 13:50:48 +09:00
2015-05-10 20:03:16 +02:00
2015-03-03 07:12:16 +00:00
2013-11-09 07:45:00 +01:00
2015-04-08 07:50:41 +00:00
2008-11-14 16:59:34 -08:00
2009-03-27 20:20:10 -07:00
2015-07-06 01:47:38 +00:00
2015-08-05 10:22:03 +09:00

Gerrit Code Review

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

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 Buck and run the following:

    git clone --recursive https://gerrit.googlesource.com/gerrit
    cd gerrit && buck build all

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

NOTE: release is optional. Last released package of the version is installed if the release number is omitted.

Events

  • November 7-8 2015: Gerrit User Conference, Mountain View. (Register).
  • November 9-13 2015: Gerrit Hackathon, Mountain View. (Invitation Only).
  • March 2016: Gerrit Hackathon, Berlin. (Details to be confirmed).
Description
RETIRED, Gerrit as used by OpenStack
Readme 120 MiB