Google Git
Sign in
gerrit / gerrit / 718b344c7a26755d562f9f2bf3671fedcf37bafc
commit718b344c7a26755d562f9f2bf3671fedcf37bafc[log] [tgz]
authorLuca Milanesio <luca.milanesio@gmail.com>Fri Jun 28 23:03:26 2024 +0100
committerGerrit Code Review <noreply-gerritcodereview@google.com>Fri Jun 28 22:03:26 2024 +0000
treead4b9d6a0b310fb67cb3b054790237c1f572bdb4
parent643f7ca24c07d9dc9162fe51d176479c14bb4d12 [diff]
Update git submodules

* Update plugins/replication from branch 'master'
  to 05c096ed827467645776abcec6b39523b4e76843
  - Move ReplicationQueue and associated bindings to ReplicationModule
    
    During the refactoring in I8003ec6c827f the ReplicationQueue and its
    associated bindings were moved to the ReplicationConfigModule for
    allowing the users of the replication APIs to be able to have the
    full bindings of all the internal replication plugin mechanisms.
    
    However, the change was reverted in I461cd1bef because of the
    breakages generated and later a new approch has been introduced
    with I349461e29d where the APIs are exposed via DynamicItem<>
    and the caller isn't required anymore to have the full Guice
    bindings to re-create the replication objects.
    
    As a result, the bindings of the replication plugin internals
    remained in the ReplicationConfigModule with nasty consequences
    of other plugins (e.g. pull-replication) to inadvertently generate
    just-in-time bindings of the replication plugin classes.
    
    When using the pull-replication and replication plugins together
    the just-in-time bindings would then eventually conflict
    with the explicit bindings done in the replication plugin.
    
    Example:
    
    [2024-06-27T22:23:19.471+01:00] [main] WARN  com.google.gerrit.server.plugins.PluginLoader : Cannot load plugin replication
    com.google.inject.CreationException: Unable to create injector, see the following errors:
    
    1) [Guice/JitBindingAlreadySet]: A just-in-time binding to DynamicSet<ReplicationStateListener> was already configured on a parent injector.
      at DynamicSet.setOf(DynamicSet.java:88)
    
    1 error
    DynamicSet:               "com.google.gerrit.extensions.registration.DynamicSet"
    ReplicationStateListener: "com.googlesource.gerrit.plugins.replication.ReplicationStateListener"
    
    By moving back the replication plugin internal classes
    bindings into its proper ReplicationModule the problem is fully
    resolved and there aren't just-in-time bindings created
    implicitly anymore.
    
    Change-Id: I2bf9dab0d2555310b4d1b0c66528b2aaa2cc5106
1 file changed
tree: ad4b9d6a0b310fb67cb3b054790237c1f572bdb4
  1. .github/
  2. .settings/
  3. .ts-out/
  4. antlr3/
  5. contrib/
  6. Documentation/
  7. e2e-tests/
  8. java/
  9. javatests/
  10. lib/
  11. modules/
  12. plugins/
  13. polygerrit-ui/
  14. prolog/
  15. prologtests/
  16. proto/
  17. resources/
  18. tools/
  19. webapp/
  20. polymer-bridges
  21. .bazelignore
  22. .bazelproject
  23. .bazelrc
  24. .bazelversion
  25. .editorconfig
  26. .git-blame-ignore-revs
  27. .gitignore
  28. .gitmodules
  29. .gitreview
  30. .mailmap
  31. .pydevproject
  32. .zuul.yaml
  33. BUILD
  34. COPYING
  35. INSTALL
  36. Jenkinsfile
  37. MODULE.bazel
  38. package.json
  39. README.md
  40. SUBMITTING_PATCHES
  41. version.bzl
  42. web-dev-server.config.mjs
  43. WORKSPACE
  44. yarn.lock
README.md

Gerrit Code Review

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

Build Status Maven Central

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 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 --recurse-submodules 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 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.