fc9d1ae55f
Setting to NOTE_DB means new changes will never be written to ReviewDb. Update ChangeNotes.Factory to properly detect the case of a change not existing in ReviewDb but possibly still existing in NoteDb. This config option only controls the primary storage for new changes. Old changes (that have not been migrated, which is all of them since this change predates the migration tools) keep their primary storage as REVIEW_DB. This means that a single running server needs to be able to handle a mix of NOTE_DB/REVIEW_DB changes. Thus we need to continue using a live ReviewDb instance in the server, and just avoid writing any NoteDb-primary changes to that instance. The easiest way to implement this technically is to keep all the BatchUpdate code the same but only commit the change transaction if the change requires ReviewDb. This means we don't have to change any BatchUpdate.Op implementations, they can continue unconditionally writing. Rolling back the transaction is much simpler than creating some kind of ReviewDb wrapper that drops writes on the floor, even though it does technically create some database traffic even though no writes are committed. Add a new NoteDbMode to run all tests with this option enabled, double-checking after the tests that no changes were stored in ReviewDb. Tweak tests in various ways to work with this option enabled, avoiding direct use of ReviewDb when the primary storage is NoteDb. Change-Id: I9caf13192f955c4ec90409da32609d0a6f496d96
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>]
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.