Go to file
Dave Borowitz 2443905d17 Test conversion of corrupt changes with GERRIT_CHECK_NOTEDB
ConsistencyCheckerIT creates various kinds of corrupt changes that we
think might exist in the wild. In most cases, the right thing to do
when converting these changes is to do our best and store *something*
in NoteDb, even if it can't be successfully read back. At the very
least this allows admins to go in and manually edit the change, using
interactive rebase in the same way they might poke the SQL database
today. This is preferable to throwing the data away during conversion.

The one time we can't do this is when the change belongs to a deleted
project. For now, we actually just discard these changes.

Rework the NoteDbChecker loops so that we attempt to convert all
changes before checking any. This doesn't make ConsistencyCheckerIT
pass, but it does let us verify from the stack trace that all
conversions were successful, even though changes couldn't be read
back.

Change-Id: I87caa451db4e049fa3fc494b79c6c036fba36b1a
2016-03-14 19:10:17 +01:00
2016-03-11 11:13:22 -05:00
2016-03-10 12:42:51 +00:00
2016-03-10 12:42:51 +00:00
2016-03-10 15:22:46 +09:00
2016-03-10 12:42:51 +00:00
2016-03-11 11:38:13 +09:00
2016-01-28 03:12:05 +00:00
2015-03-03 07:12:16 +00:00
2013-11-09 07:45:00 +01:00
2016-02-12 11:49:00 +01:00
2008-11-14 16:59:34 -08:00
2009-03-27 20:20:10 -07:00
2016-01-07 21:29:47 +01:00
2016-03-10 12:42:51 +00: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 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>]

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

Events

  • March 14-18 2016: Gerrit Hackathon, Berlin (free seats are still available).
Description
RETIRED, Gerrit as used by OpenStack
Readme 120 MiB