Google Git
Sign in
gerrit / gerrit / 5b8099c9c3640dd86eacc576116a38e4b7dec336
commit5b8099c9c3640dd86eacc576116a38e4b7dec336[log] [tgz]
authorEdwin Kempin <ekempin@google.com>Fri Dec 29 11:28:38 2023 +0000
committerEdwin Kempin <ekempin@google.com>Fri Dec 29 11:28:38 2023 +0000
treea510f9d45c2556477791ed2f8ae223a486ec23be
parent8ca01c5dd51d4bc937f0edbd6abbf2f4235f3f6e [diff]
Document how to make an account visible to all users when VISIBLE_GROUP is used

At Google it's a common workflow that service accounts are used to
automatically assign a change to a reviewer (e.g. the user adds the
service account as a reviewer, then that service will assign the change
to a human reviewer). This only works if the service account is visible
to all users. Document how to make an account visible to all users if
VISIBLE_GROUP is configured for accounts.visibility, which is the
account visibility that is used at Google.

Release-Notes: skip
Bug: Google b/313411537
Change-Id: I74e3a3c73be7dc4540ded454bd382b18c08155cd
Signed-off-by: Edwin Kempin <ekempin@google.com>
1 file changed
tree: a510f9d45c2556477791ed2f8ae223a486ec23be
  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. MODULE.bazel
  36. package.json
  37. README.md
  38. SUBMITTING_PATCHES
  39. version.bzl
  40. web-dev-server.config.mjs
  41. WORKSPACE
  42. 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.