Google Git
Sign in
gerrit / gerrit / d32aedb347cc18289d64ee84d8ac66677e0bfdad
commitd32aedb347cc18289d64ee84d8ac66677e0bfdad[log] [tgz]
authorMaxime Guerreiro <maximeg@google.com>Thu Mar 22 15:29:10 2018 +0100
committerMaxime Guerreiro <maximeg@google.com>Tue Apr 10 14:56:03 2018 +0000
tree8eee5d0b95a12cf5e1960d0423e136e21f19a3b9
parent9d72988a56e753be476bc5d235afe3334fce1326 [diff]
Expose the submit requirements in the Change API

Add requirements in the Change API, allowing PolyGerrit and API
consumers to use this information, and hopefuly improve communication
with the final users (change owner and contributors).
The API is thought to be both human and programs friendly, by exposing
a human readable description, a "type" identifying accurately the
requirement, and additional values in a key-value fashion.

For instance, the PolyGerrit UI might use these informations to display
each requirement with markup depending on its type, and fallback on the
fallbackText if the type is unknown (hence the name).

Change-Id: Ifb9e15a3c08ebaf42d8eb1469257c6e41cc22882
5 files changed
tree: 8eee5d0b95a12cf5e1960d0423e136e21f19a3b9
  1. .settings/
  2. antlr3/
  3. contrib/
  4. Documentation/
  5. gerrit-gwtdebug/
  6. gerrit-gwtui/
  7. gerrit-gwtui-common/
  8. gerrit-plugin-gwtui/
  9. java/
  10. javatests/
  11. lib/
  12. plugins/
  13. polygerrit-ui/
  14. prolog/
  15. prologtests/
  16. resources/
  17. tools/
  18. webapp/
  19. .bazelproject
  20. .editorconfig
  21. .git-blame-ignore-revs
  22. .gitignore
  23. .gitmodules
  24. .mailmap
  25. .pydevproject
  26. BUILD
  27. COPYING
  28. INSTALL
  29. README.md
  30. SUBMITTING_PATCHES
  31. version.bzl
  32. 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 --recursive 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.