commit | 35c76c07b71e95e0619639c000d00e93201fed4f | [log] [tgz] |
---|---|---|
author | Dave Borowitz <dborowitz@google.com> | Fri Jun 23 13:14:49 2017 -0400 |
committer | David Ostrovsky <david@ostrovsky.org> | Sat Jun 24 07:04:32 2017 +0200 |
tree | f82c99e18b14bfd680e2cc7831be6233dfd77ae4 | |
parent | d91ca59d6b8236d48b2f915b0de5a27f028cb435 [diff] |
Support reindexing immediately after NoteDb upgrade There are two reasons to support this. One is for an offline upgrade to NoteDb at a released Gerrit version, where we fully expect there to be index schema changes in addition to the NoteDb migration. Just kicking off Reindex immediately after MigrateToNoteDb saves the user an extra manual invocation. That is implemented in this change. The other scenario is an online NoteDb migration in conjunction with an online schema upgrade, where we don't want to increase contention by running the migration and reindex concurrently. Implementing this will require managing more subtle interactions between LifecycleListeners, and is not implemented in this change. We literally invoke Reindex's main method rather than trying to do something smarter like reusing the injector stack from MigrateToNoteDb, because Reindex has a custom set of modules for managing the index versions. At that point, we could either factor out a variant of Reindex#run that takes some arguments, or just do a tiny amount of string manipulation. I went with the latter. Change-Id: Idf8d0513a08db8bb9e7efda1cf2a12e0579b2fee
Gerrit is a code review and project management tool for Git based projects.
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.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
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.
The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recursive https://gerrit.googlesource.com/gerrit cd gerrit && bazel build release
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>]
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.