Google Git
Sign in
gerrit / gerrit / 5ccf0b9e39afc9372d9867c4337e81751bbcbd8b
commit5ccf0b9e39afc9372d9867c4337e81751bbcbd8b[log] [tgz]
authorMaxime Guerreiro <maximeg@google.com>Tue May 15 16:28:22 2018 +0000
committerMaxime Guerreiro <maximeg@google.com>Wed Jun 06 16:20:00 2018 +0000
tree866472fe09bb13162a0885d3304509cfa770d910
parenteaa1783b24f0cc419fab02342eddbe20a150f7d9 [diff]
Enable plugins in BATCH mode

Batch mode is defined (for now) as "everything that is not Gerrit
Daemon". This includes the "reindex" task, but is not limited to it.

Adding plugins to batch mode allows plugins with a direct impact on
the changes' index to have a consistent impact: without it, custom
prolog predicates and plugin-provided SubmitRule-s are ignored.

In BATCH mode, Gerrit will try to find and load Gerrit-BatchModule(s)
modules defined by plugins, if any. This module should be compatible
with the batch mode injectors: it must not rely on SSH or HTTP classes.
This new module is optional, and plugins not defining one will not be
loaded in batch mode. As such, this new feature is retro-compatible: no
"old" plugins will be loaded.

Change-Id: I9be5a2ea0fd841986b940e046d215a820497107b
5 files changed
tree: 866472fe09bb13162a0885d3304509cfa770d910
  1. .settings/
  2. antlr3/
  3. contrib/
  4. Documentation/
  5. gerrit-elasticsearch/
  6. gerrit-gwtdebug/
  7. gerrit-gwtui/
  8. gerrit-gwtui-common/
  9. gerrit-plugin-gwtui/
  10. gerrit-server/
  11. java/
  12. javatests/
  13. lib/
  14. plugins/
  15. polygerrit-ui/
  16. prolog/
  17. prologtests/
  18. proto/
  19. resources/
  20. tools/
  21. webapp/
  22. .bazelproject
  23. .editorconfig
  24. .git-blame-ignore-revs
  25. .gitignore
  26. .gitmodules
  27. .mailmap
  28. .pydevproject
  29. 0001-Replace-native-http-git-_archive-with-Skylark-rules.patch
  30. BUILD
  31. COPYING
  32. INSTALL
  33. README.md
  34. SUBMITTING_PATCHES
  35. version.bzl
  36. 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.