Google Git
Sign in
gerrit / gerrit.git / d9df9ef233457266f370dc75056f17dea60d602a
commitd9df9ef233457266f370dc75056f17dea60d602a[log] [tgz]
authorDavid Pursehouse <dpursehouse@digital.ai>Fri May 22 20:40:57 2020 +0900
committerGerrit Code Review <noreply-gerritcodereview@google.com>Fri May 22 11:40:57 2020 +0000
tree26a0aee7498e8807643a26ff87b691cd8648f25f
parent7b6db6b5e547259225ccefc34d44cb34604cef43 [diff]
Update git submodules

* Update plugins/replication from branch 'stable-3.1'
  to b303e1b2963ef5c344ec4bd98e90ff0c80516162
  - Merge branch 'stable-3.0' into stable-3.1
    
    * stable-3.0:
      Make persistent task keys stable
    
    Change-Id: I2cf44bc4e9810c83fa7afee4290fca25dc50724b
    
  - Merge branch 'stable-2.16' into stable-3.0
    
    * stable-2.16:
      Make persistent task keys stable
    
    Change-Id: Iefda465c739f4669b5394d3c57f7abe0d7513b5f
    
  - Make persistent task keys stable
    
    GSON was used to create json as the input for sha1 task keys, however
    gson can order the json keys differently anytime. Use the values in a
    specific order to create stable keys.
    
    Bug: Issue 11760
    Change-Id: I6900b5ddb3ba8ab7b5cf7803ae9dd551b5980a59
1 file changed
tree: 26a0aee7498e8807643a26ff87b691cd8648f25f
  1. .settings/
  2. antlr3/
  3. contrib/
  4. Documentation/
  5. e2e-tests/
  6. java/
  7. javatests/
  8. lib/
  9. modules/
  10. plugins/
  11. polygerrit-ui/
  12. prolog/
  13. prologtests/
  14. proto/
  15. resources/
  16. tools/
  17. webapp/
  18. .bazelignore
  19. .bazelproject
  20. .bazelrc
  21. .bazelversion
  22. .editorconfig
  23. .git-blame-ignore-revs
  24. .gitignore
  25. .gitmodules
  26. .gitreview
  27. .mailmap
  28. .pydevproject
  29. .zuul.yaml
  30. BUILD
  31. COPYING
  32. INSTALL
  33. Jenkinsfile
  34. package.json
  35. README.md
  36. SUBMITTING_PATCHES
  37. version.bzl
  38. 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 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.