Google Git
Sign in
gerrit / gerrit / 5ecb6422b6ca2b08ea51a32098c151fd07307f70
commit5ecb6422b6ca2b08ea51a32098c151fd07307f70[log] [tgz]
authorChangcheng Xiao <xchangcheng@google.com>Tue Jan 15 17:17:04 2019 +0100
committerChangcheng Xiao <xchangcheng@google.com>Tue Jan 15 18:22:49 2019 +0100
tree5fce898c4dba95bb88d042f9a7b821d7294ceb6a
parent7b78caf7420af0c9016691de2d8a49efd0574962 [diff]
Move docs about project state to "config-project-config.txt"

We have two documents, e.g. "config-project-config.txt" and
"project-configuration.txt", containing doc for project
configs. "config-project-config.txt" intends to document
avaliable configs to the project through "project.config",
"rules.pl" and "groups" file. "project.configuration" intends
to document the configs avaliable through the UI. However,
both of them are not complete, making it hard for users to
learn how to config their projects.

This commit and followup commits proposes to move docs
about "Project Options" in "project-configuration.txt" to
"config-project-config.txt" and then just referencing them
from "project-configuration.txt". Hopefully, this could
make it easier for users to understand Gerrit project configs.

Change-Id: I0cf5013bd5260cf69cdb6e8ec51608cfc1d59d79
2 files changed
tree: 5fce898c4dba95bb88d042f9a7b821d7294ceb6a
  1. .settings/
  2. antlr3/
  3. contrib/
  4. Documentation/
  5. java/
  6. javatests/
  7. lib/
  8. plugins/
  9. polygerrit-ui/
  10. prolog/
  11. prologtests/
  12. proto/
  13. resources/
  14. tools/
  15. webapp/
  16. .bazelproject
  17. .bazelrc
  18. .editorconfig
  19. .git-blame-ignore-revs
  20. .gitignore
  21. .gitmodules
  22. .mailmap
  23. .pydevproject
  24. BUILD
  25. COPYING
  26. INSTALL
  27. README.md
  28. SUBMITTING_PATCHES
  29. version.bzl
  30. WORKSPACE
README.md

Gerrit Code Review

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

Build Status

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 IRC channel on freenode is #gerrit. An archive is available at: echelog.com.

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 7 based Gerrit image:

    docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]

To run a Ubuntu 15.04 based Gerrit image:

    docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]

NOTE: release is optional. Last released package of the version is installed if the release number is omitted.