Update git submodules

* Update plugins/delete-project from branch 'master'
  to 75b79c115ba3dd03aa56a3165e6c319fa30c6c4a
  - Merge branch 'stable-3.8'
    * stable-3.8:
      ConfigurationTest: Remove flaky invalidTargetArchiveFolder test
      Send Project Deleted Events also when archiving
    Change-Id: Ic64ac7317f430f520ef0350c0bbdb63846823086
  - Merge branch 'stable-3.7' into stable-3.8
    * stable-3.7:
      ConfigurationTest: Remove flaky invalidTargetArchiveFolder test
      Send project-deleted event after project deletion
    Change-Id: I2ac01b00d7ce442b96a032d90b4037670e65d79a
  - ConfigurationTest: Remove flaky invalidTargetArchiveFolder test
    This test is failing when running gerrit test in docker image with root
    user. It's also failing when remote build execution is used (BuildBuddy
    It seems to rely on the fact that the exception is thrown:
    java.nio.file.FileSystemException: /\\\: Operation not permitted
    However when the test is executed with BuildBuddy RBE that exception is
    not raised and as a consequence of that the test ends up failing. It
    looks that the folder /\\\ is created in the remote executor.
    While it could be fixed with:
    exec_properties = {
        "dockerUser": "nobody",
    we prefer not to complicate our build toolchain and rather remove the
    Change-Id: I51bccdf2cb19559690d3d88bd92cf60bc28f5fcd
  - Send Project Deleted Events also when archiving
    When projects are either deleted fully, or preserved by setting as
    hidden and moving to f.i. Deleted-Projects, we send a Project Deleted
    Event. We do not do the same if we archive the repository, even though
    this is effectively also a deleted project (more so than hidden is) from
    a Gerrit perspective.
    Not sending this event means that archived repositories are not properly
    removed from replicas when replicateRepositoryDeletions is set.
    This makes sure that we still send the projectDeletionEvent while
    archiving is set.
    Release-Notes: Plugin Delete-Project archiveDeletedRepos option now also emits a Project Deletion event.
    Change-Id: I0829a1a2016d67ac789b92f67d1d7c6a13b65c65
1 file changed
tree: c202c409b6af3dc8220a1cdfbe71201fa493e86f
  1. .settings/
  2. .ts-out/
  3. antlr3/
  4. contrib/
  5. Documentation/
  6. e2e-tests/
  7. java/
  8. javatests/
  9. lib/
  10. modules/
  11. plugins/
  12. polygerrit-ui/
  13. prolog/
  14. prologtests/
  15. proto/
  16. resources/
  17. tools/
  18. webapp/
  19. .bazelignore
  20. .bazelproject
  21. .bazelrc
  22. .bazelversion
  23. .editorconfig
  24. .git-blame-ignore-revs
  25. .gitignore
  26. .gitmodules
  27. .gitreview
  28. .pydevproject
  29. .zuul.yaml
  30. BUILD
  33. Jenkinsfile
  34. MODULE.bazel
  35. package.json
  36. README.md
  38. version.bzl
  39. web-dev-server.config.mjs
  41. yarn.lock

Gerrit Code Review

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

Build Status Maven Central


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.

Reporting bugs

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.

Getting in contact

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

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.