e7042be5cb
The basic process is a loop over the possible NotesMigrationStates, starting with the current state in gerrit.config, where each step runs some process and updates the config to the next state. This works by directly editing gerrit.config on disk after the migration work completes, which means that migrations are easily resumable. In theory, this process could be customized by telling it to stop at any of the intermediate states, reexecute certain phases where that makes sense, etc. However, that would result in significant configuration complexity, and we don't want to burden admins with too many flags. That said, based on our experience manually executing the migration steps on googlesource.com, there are two flags we want to support. First is the idea of a "trial mode": admins can try turning on NoteDb to see if performance, resource usage, or any other behavior is acceptable, but leave ReviewDb the source of truth. This terminates the migration in NotesMigrationState.READ_WRITE_NO_SEQUENCE. Second, we can force rebuilding of some or all changes, as long as we're sure that ReviewDb is still the source of truth. This is primarily useful for developers and debugging issues with the rebuild process (which, having migrated googlesource.com, we're fairly confident in, but we're prepared to be surprised). This implementation is just a skeleton: the loop handles all the currently-supported states, but many transitions throw UnsupportedOperationException. It also notably does not work properly in a running server, since it only updates gerrit.config and not the NotesMigration singleton. Change-Id: Ic83071c794bcddc6076306215c2e445fedffbc93
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 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.