Google Git
Sign in
gerrit / gerrit / 3f46efd5653c87a3519fff1281329484b7d1f4e0
commit3f46efd5653c87a3519fff1281329484b7d1f4e0[log] [tgz]
authorMarco Miller <marco.miller@ericsson.com>Sat Feb 01 11:06:11 2020 -0500
committerMarco Miller <marco.miller@ericsson.com>Sun Feb 02 17:48:19 2020 -0500
tree4e9b7b2b9f4db0c0bad033958e2ef61d4a957f87
parent4aaa88829abe7c728f7eaf6736f120bff586ac0c [diff]
e2e-tests: Introduce example to test local setups

Add the CloneUsingBothProtocols scenario class with its json file
companion. Propose a reusable way to code such classes, at least
initially, through that example class and json. Keep the corresponding
refactoring of their sibling ReplayRecordsFromFeederScenario files for
follow-up changes.

Use that simple and no-load CloneUsingBothProtocols scenario in the
documentation. Foster using that one instead to validate local setups.
As one's local setup gets tested that way, foster developing more
scenarios.

Change-Id: I39fae723a81633a49327e509a99269ba028dcbdf
3 files changed
tree: 4e9b7b2b9f4db0c0bad033958e2ef61d4a957f87
  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.