Google Git
Sign in
gerrit / gerrit / dd31db99c33be54ea6fabd3cfd57ee08d05c9b52
commitdd31db99c33be54ea6fabd3cfd57ee08d05c9b52[log] [tgz]
authorGal Paikin <paiking@google.com>Fri Dec 06 14:43:35 2019 +0100
committerGal Paikin <paiking@google.com>Tue Dec 10 15:05:08 2019 +0100
treecbe21d5688a5ee6d9ac9a9e6334be03210142ac9
parentc8a7bfff952e00f63508d0bc6d141cda5b01dd6e [diff]
Change the structure of Submission Id

Currently Submission Id is constructed by the change-id of the change
that triggered the submission, the timestamp, and a random alphanumeric
string. This is not pretty. Since we recently revealed the submission id
via ChangeInfo in Ic557e0c94 and via queries in I337f7f8ae, it's a good
idea to change the submission id to be more user friendly.

Submission Id is now constructed of "<numeric-id>-<topic>" or
"<numeric-id>" if topic doesn't exist for that change.

The change id is used because it makes the submission id unique (a
change can only be submitted once). The topic is used mostly since this
is currently one of the main use cases for Revert Submission.

Change-Id: Iec8b0db66adf9a7ff2809994acaedef09e4e885c
16 files changed
tree: cbe21d5688a5ee6d9ac9a9e6334be03210142ac9
  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. BUILD
  30. COPYING
  31. INSTALL
  32. Jenkinsfile
  33. package.json
  34. README.md
  35. SUBMITTING_PATCHES
  36. version.bzl
  37. 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.