Google Git
Sign in
gerrit / gerrit / b52205ffb0f873fb5dffba9f4c7a2c2c97cb99cb
commitb52205ffb0f873fb5dffba9f4c7a2c2c97cb99cb[log] [tgz]
authorDave Borowitz <dborowitz@google.com>Thu Jun 22 17:03:45 2017 -0400
committerDave Borowitz <dborowitz@google.com>Fri Jun 23 15:59:09 2017 -0400
treeb38b6b24b7360563c99034c75c807132295c4ed2
parentf7cc0f4043b2476e4cd0a64b79ccc3078edcfa5a [diff]
Finish NoteDbMigrator

The final phase is converting all changes to NoteDb primary. This is
very straightforward, as PrimaryStorageMigrator was designed to be run
in arbitrary order with arbitrary parallelism.

The only tricky thing is that this phase changes to _NOTE_DB_PRIMARY
before doing any work, then NOTE_DB(_UNFUSED) after. The only way it's
possible to iterate through the main state loop in _PRIMARY is if there
was a failure, in which case we run the failed step again on the next
execution.

This exposed one now-faulty assumption in the NoteDbBatchUpdate
implementations that the specific ReviewDb instance handed to the
constructor has its changes tables disabled. It's possible for the
config read from the NotesMigration to determine which BatchUpdate
implementation to use to differ from the bits used by
NotesMigrationSchemaFactory at context creation time to open a ReviewDb.
There's no harm in removing these overly-conservative checks.

Change-Id: I0a7def4dc7e1da18eb928920b2538225fc6fea57
4 files changed
tree: b38b6b24b7360563c99034c75c807132295c4ed2
  1. .settings/
  2. contrib/
  3. Documentation/
  4. gerrit-acceptance-framework/
  5. gerrit-acceptance-tests/
  6. gerrit-antlr/
  7. gerrit-cache-h2/
  8. gerrit-common/
  9. gerrit-elasticsearch/
  10. gerrit-extension-api/
  11. gerrit-gpg/
  12. gerrit-gwtdebug/
  13. gerrit-gwtexpui/
  14. gerrit-gwtui/
  15. gerrit-gwtui-common/
  16. gerrit-httpd/
  17. gerrit-launcher/
  18. gerrit-lucene/
  19. gerrit-main/
  20. gerrit-oauth/
  21. gerrit-openid/
  22. gerrit-patch-commonsnet/
  23. gerrit-patch-jgit/
  24. gerrit-pgm/
  25. gerrit-plugin-api/
  26. gerrit-plugin-gwtui/
  27. gerrit-prettify/
  28. gerrit-reviewdb/
  29. gerrit-server/
  30. gerrit-sshd/
  31. gerrit-test-util/
  32. gerrit-util-cli/
  33. gerrit-util-http/
  34. gerrit-util-ssl/
  35. gerrit-war/
  36. lib/
  37. plugins/
  38. polygerrit-ui/
  39. ReleaseNotes/
  40. tools/
  41. website/
  42. .bazelproject
  43. .editorconfig
  44. .git-blame-ignore-revs
  45. .gitignore
  46. .gitmodules
  47. .mailmap
  48. .pydevproject
  49. BUILD
  50. COPYING
  51. INSTALL
  52. README.md
  53. SUBMITTING_PATCHES
  54. version.bzl
  55. WORKSPACE
README.md

Gerrit Code Review

Gerrit is a code review and project management tool for Git based projects.

Build Status

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.