Google Git
Sign in
gerrit / gerrit / 5d5c159bb912d1ba3d653a6760d739d79d7964dc
commit5d5c159bb912d1ba3d653a6760d739d79d7964dc[log] [tgz]
authorFabio Ponciroli <ponch78@gmail.com>Fri Sep 08 11:46:03 2023 +0200
committerFabio Ponciroli <ponch78@gmail.com>Tue Sep 19 13:06:08 2023 +0000
tree01bc95cdc0b3f76b1f213ba07b5ca680f8b27562
parentf1bb68e9ea663cd4cce35cc225a6dccdf74c119d [diff]
Make Draft Comment events publishing configurable

The extra ref-updates will add more events in the
the stream-events.

This might cause problems in some system because of:
* extra load: in GerritHub `refs/draft-comments/` can be up to
  the 5% of the overall amount of stream events.
  In busier installation the extra load might be more
  and create performance issues;
* non-resilient plugins: plugins might not be resilient in processing
  new refs. Having the new refs production configurable can
  be useful to avoid, or at least minimize, breakage
  in downstream system during upgrades.

Release-Notes: Make Draft Comment events publishing configurable
Change-Id: I02e17592b78c6b3bf80bff5a0ab666389e21669d
3 files changed
tree: 01bc95cdc0b3f76b1f213ba07b5ca680f8b27562
  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. polymer-bridges
  20. .bazelignore
  21. .bazelproject
  22. .bazelrc
  23. .bazelversion
  24. .editorconfig
  25. .git-blame-ignore-revs
  26. .gitignore
  27. .gitmodules
  28. .gitreview
  29. .pydevproject
  30. .zuul.yaml
  31. BUILD
  32. COPYING
  33. INSTALL
  34. Jenkinsfile
  35. package.json
  36. README.md
  37. SUBMITTING_PATCHES
  38. version.bzl
  39. web-dev-server.config.mjs
  40. WORKSPACE
  41. 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.