Google Git
Sign in
gerrit / gerrit / e5bd86b4e2cacac0d55db421154f9a518aaa0167
commite5bd86b4e2cacac0d55db421154f9a518aaa0167[log] [tgz]
authorLuca Milanesio <luca.milanesio@gmail.com>Tue Jul 23 16:01:32 2024 +0100
committerLuca Milanesio <luca.milanesio@gmail.com>Tue Jul 23 15:27:07 2024 +0000
treed72f16d23bc06cd22ca1f77f33f2f67795f424b9
parentebfe1bf8ae18daea1f17418a2abee2151cf855e9 [diff]
Make explicit the Gerrit support for Windows Server

Gerrit documentation has several references on how to setup
the service on Windows Server, making the reader thinking it as
a valid option for a production setup.

Gerrit isn't actively tested on the CI/CD on Windows Server
and its releases not validated end-to-end. There is also
a very limited adoption from the community therefore the
feedback on potential issues is very limited.

Add an explicit note on the current situation with Windows
Server so that Gerrit admins are warned on the risks associated.

Release-Notes: Add warning about choosing Windows as server-side platform for running Gerrit
Change-Id: I408c4a8ec3f2a3aa4552b5d8cbfcd981c17e5b89
4 files changed
tree: d72f16d23bc06cd22ca1f77f33f2f67795f424b9
  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. .mailmap
  30. .pydevproject
  31. .zuul.yaml
  32. BUILD
  33. COPYING
  34. INSTALL
  35. Jenkinsfile
  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.