2bdaa68b4a
To support a live migration on a multi-master Gerrit installation, the
upgrade is done in 2 steps:
- part 1 (this change):
* always write to both backends (database and git)
* a configuration option (user.readStarredChangesFromGit) decides if
the starred changes are read from database or git (default:
database)
* upgraded instances write to both backends, old instances only
read/write from/to the database
* after upgrading all instances (all still read from the database)
run a batch to copy all starred changes from the database to git
* update all instances to read from git
* make sure all instances use the new schema version
- part 2 (next change):
* bump the database schema version
* migrate the starred changes from database to git (for single
instance Gerrit servers)
* delete the database table
* delete the user.readStarredChangesFromGit config option
The user.readStarredChangesFromGit configuration options is replacing
the global readAccounts bit from NotesMigration in
StarredChangesUtil. This way we can migrate the starred changes
already now while other account data is still in the database.
Change-Id: Iac4f68ea6e0c65b589de25013bfffdcd0fca0d38
Signed-off-by: Edwin Kempin <ekempin@google.com>
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.