Google Git
Sign in
gerrit / gerrit / ef1b811d6d3b34b9de9e0aae93531d93e88fc34f
commitef1b811d6d3b34b9de9e0aae93531d93e88fc34f[log] [tgz]
authorEdwin Kempin <ekempin@google.com>Tue Oct 29 09:27:00 2019 +0100
committerEdwin Kempin <ekempin@google.com>Tue Oct 29 12:49:09 2019 +0100
tree847f6695f1593619b64ff1523a95efac4360efb8
parent6072b4b201ec2b32a3cad24cac4c8ec8f3fb7933 [diff]
Start a separate documentation page for core plugins

Core plugins are described as part of the plugin config documentation.
The purpose of the plugin config documentation is to give an overview of
all plugins and which functionality they provide. Defining what core
plugins are doesn't really fit into this page. A separate documentation
page for core plugins makes sense since we intend to expand this
documentation. We want to define more clearly what a core plugin is,
what criteria a plugin must fulfill to become a core plugin and
processes around core plugins. All this newly planned documentation
around core plugins is surely out of scope for the plugin config
documentation, hence we want to have a new page for this.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: If6f1867cd4ec0a5843080e094cb397c30af99db8
4 files changed
tree: 847f6695f1593619b64ff1523a95efac4360efb8
  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.