| commit | 73007307c4bbb0a287e2e20a17fd9dadd39019d9 | [log] [tgz] |
|---|---|---|
| author | Dave Borowitz <dborowitz@google.com> | Mon Oct 30 15:53:33 2017 -0400 |
| committer | Dave Borowitz <dborowitz@google.com> | Wed Nov 01 12:46:25 2017 -0400 |
| tree | 3318dd9c69f4f1860921a012b02da70c48a61159 | |
| parent | 528b4d257b4f017ef003e92cba0b2fa53278304a [diff] |
NoteDbMigrator: Use one NoteDbUpdateManager per project We want to avoid writing out thousands of loose objects during migration by using a custom ObjectInserter implementation. This wouldn't do any good if NoteDbMigrator created a new NoteDbUpdateManager with a new ObjectInserter for each change. Hoist manager creation into NoteDbMigrator instead, even though this requires repeating a bit of logic that previously lived in ChangeRebuilderImpl. The old implementation of NoteDbUpdateManager unconditionally buffered in memory all objects that were inserted, so it could expose them in the StagedResult used by the auto-rebuilding and dry-run codepaths. This behavior is reasonable when modifying a small number of changes, but would not be appropriate for a batch migration where the manager is used to update thousands of changes in a repository. Fortunately, the InsertedObjects aren't needed in the migration codepath, so we can just add a flag to NoteDbUpdateManager to turn this behavior off. Similarly, plumb a flag to NoteDbUpdateManager to turn off atomic ref updates. In an online migration, we fully expect some changes to be modified concurrently, which is already handled by later auto-rebuilding. No need to block a single giant BatchRefUpdate on such changes. Change-Id: I32446fd17d6a2b0cc8b30bd1164402580d7e0aa2
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.