Google Git
Sign in
gerrit / gerrit / cbdfd581d5783a9c2b577f4abfdaa8d37b053fc3
commitcbdfd581d5783a9c2b577f4abfdaa8d37b053fc3[log] [tgz]
authorEdwin Kempin <ekempin@google.com>Thu Sep 05 09:26:46 2019 +0200
committerEdwin Kempin <ekempin@google.com>Fri Sep 06 09:47:48 2019 +0200
tree26a20de969b8b14478c9130f77efa951adef93ae
parent6fbe4b93d1dccdb305148164660d756ebd58c9d8 [diff]
Test that creating 2 changes for the same commit on the same branch is not possible

Gerrit rejects the creation of a change for a commit that already exists
in the repository. The only exception is for changes on different
branches if CREATE_NEW_CHANGE_FOR_ALL_NOT_IN_TARGET is set to true.

Add push tests to verify this. In addition verify that it's also not
possible to end up with 2 changes for the same commit on the same branch
by using the Create Change REST endpoint, or by doing and publishing
identical change edits on different changes which were created on the
same base.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I6ed37042475250b23a08ec3318f30d538055d166
3 files changed
tree: 26a20de969b8b14478c9130f77efa951adef93ae
  1. .settings/
  2. antlr3/
  3. contrib/
  4. Documentation/
  5. java/
  6. javatests/
  7. lib/
  8. plugins/
  9. polygerrit-ui/
  10. prolog/
  11. prologtests/
  12. proto/
  13. resources/
  14. tools/
  15. webapp/
  16. .bazelproject
  17. .bazelrc
  18. .bazelversion
  19. .editorconfig
  20. .git-blame-ignore-revs
  21. .gitignore
  22. .gitmodules
  23. .gitreview
  24. .mailmap
  25. .pydevproject
  26. BUILD
  27. COPYING
  28. INSTALL
  29. package.json
  30. README.md
  31. SUBMITTING_PATCHES
  32. version.bzl
  33. 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.