Update git submodules

* Update plugins/delete-project from branch 'stable-3.9'
  to 93038507ff113042bf09ba96d788af43a5deff28
  - Update delete-project plugin following I479588df
    Bug: Google b/289357382
    Release-Notes: skip
    Change-Id: Ia047b6a5a66ff605c2e229f26928d7722a155645
    (cherry picked from commit 723264be4256494c45f5ba056e81be2ad25bbe7c)
  - Provide less verbose repo delete method
    Currently, the repo delete method exposed is too verbose, and forces
    the client to provide parameters for preserving and archiving the repo.
    Provide a less verbose method with sensible defaults.
    Annotate the method so its clear it will be used by the pull-
    replication plugin, this will also prevent accidental removal of the
    method impacting the pull-replication plugin.
    Bug: Issue 16730
    Change-Id: I50dbcb9a91bf3697b8c7d66db646020d29dae83a
    (cherry picked from commit 0322a37009071da525bfd8569e98538c2e8891d5)
  - Add IntelliJ files to gitignore
    Change-Id: I7600680cf559314356fc9478e7100918f334b9dd
    (cherry picked from commit 4b173665d13703332a941d9c347c3adddd45fb54)
  - Extract the repository deletion logic so it becomes reusable
    The code that deletes a repository is generally quite robust and
    as such it will be very useful for the pull-replication plugin.
    However, the logic is heavily baked into the plugin itself;
    it requires archiving settings read from the plugin config, and
    deletion listeners to notify downstream systems - both are not
    relevant to the pull-replication plugin (or anything else that
    might want to just delete a repo).
    Extract the repo deletion logic into a `RepositoryDelete` class,
    free from any nuances of the delete-project plugin itself, so it
    can be reused. The `FilesystemDeleteHandler` is now essentially
    delegating everything into that class. I've also taken the
    liberty to add a couple of missing tests for the notifying of
    downstream systems through the deletion listeners.
    Bug: Issue 16730
    Change-Id: Ib28dbed344ef8a419cf7c318d0e87aadd7dadd5e
    (cherry picked from commit 79674d9e00f8458a2f4f6d3a91bd032579c3f25c)
1 file changed
tree: d732c83be706721c9a2a46ab0ba5ec214d938a19
  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. package.json
  35. README.md
  37. version.bzl
  38. web-dev-server.config.mjs
  40. 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.