| commit | 2c7ff59e4b845b3b936a6d3387b1c994b59b7e3c | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Mon Feb 15 23:53:09 2021 +0000 |
| committer | David Ostrovsky <david.ostrovsky@gmail.com> | Thu Mar 04 09:56:16 2021 +0000 |
| tree | 10ff16473b1482fa09f5eac1f99cdc90094edd86 | |
| parent | 2c11c0e3c2a6e640b2f904a226362ba5618081dc [diff] |
Apply modules overrides by libModule for batch program reindex Gerrit ignores libModule overrides when running its batch programs. As a consequence, it would not allow to replace default implementation with ad-hoc modules (e.g. use a persistent cache different than H2). From Change-Id: I9be5a2ea0f Gerrit supports plugins that can provide extra BatchModules to be used by the Gerrit site programs like the reindex and during the init phase. Improve the BatchModule by enabling also the replacement of Gerrit's introducing a new LibModuleType.SYS_BATCH_MODULE called BatchModule. Allow to specify a set of alternative implementations during the Gerrit programs execution by introducing a new libBatchModule. LibModules can override any of the Gerrit tagged modules loaded by default by the BatchProgramModule. Modules can potentially provide also a different set of bindings for the daemon execution (libModule configuration) and the site program (libBatchModule configuration), so to adapt to the availability of different injected classes in the two contexts. Before this change, plugins could already expose BatchModule to be loaded in Gerrit's site programs like the reindex. This change allows Gerrit to have in addition the ability to override the tagged Modules in core with alternative implementations provided by the library. One use case is the persistent cache backend, alternative to the default H2 backend, which during reindex needs to populates the diff caches. Bug: Issue 14004 Change-Id: Ifab60ae3252d50066eb04cb02369b0ce987ee835
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 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 --recurse-submodules 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 8 based Gerrit image:
docker run -p 8080:8080 gerritcodereview/gerrit[:version]-centos8
To run a Ubuntu 20.04 based Gerrit image:
docker run -p 8080:8080 gerritcodereview/gerrit[:version]-ubuntu20
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.