Google Git
Sign in
gerrit / gerrit / 6496a17dce2d3f6abd69e060b78bce9f85d022ac
commit6496a17dce2d3f6abd69e060b78bce9f85d022ac[log] [tgz]
authorEdwin Kempin <ekempin@google.com>Thu Mar 24 10:34:29 2022 +0100
committerEdwin Kempin <ekempin@google.com>Thu Mar 24 10:48:46 2022 +0100
tree0297331ef7ed7cb9659e7dfe73cb8b5d0f804ed9
parent872edb19a111170c43c3f17be3a03c68d0689e21 [diff]
StickyApprovalsIT: Run all test cases with and without copy condition

This is to ensure that the behaviour of copy conditions is consistent
with the behaviour of the corresponding boolean flags. This is important
as we plan to migrate the boolean flags to copy conditions and we do not
want to break the current behaviour by doing this.

Having all tests run with a copy condition is also a preparation to drop
support for the boolean flags at some point. Now we can do this without
needing to rewrite/adapt any of the tests (but we only need to drop the
*_withoutCopyConditions tests).

The stickyWhenCopyConditionIsTrue test is dropped since what was tested
here is now better covered by the other tests the run with copy
conditions.

There is one small inconsistency between has:unchanged-files and
setCopyAllScoresIfListOfFilesDidNotChange=true (the former ignores magic
files, while the other doesn't). This difference doesn't matter much for
the migration as it covers an edge case (merge commit is replaced by a
non-merge commits and no files changed except /MERGE_LIST) and should
occur only very seldom. Hence this test is only executed with copy
condition.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I37e959adbc3a08bc8d7d7052782265636d3feeb3
Release-Notes: skip
1 file changed
tree: 0297331ef7ed7cb9659e7dfe73cb8b5d0f804ed9
  1. .settings/
  2. .ts-out/
  3. antlr3/
  4. contrib/
  5. Documentation/
  6. e2e-tests/
  7. java/
  8. javatests/
  9. lib/
  10. modules/
  11. plugins/
  12. polygerrit-ui/
  13. prolog/
  14. prologtests/
  15. proto/
  16. resources/
  17. tools/
  18. webapp/
  19. polymer-bridges
  20. .bazelignore
  21. .bazelproject
  22. .bazelrc
  23. .bazelversion
  24. .editorconfig
  25. .git-blame-ignore-revs
  26. .gitignore
  27. .gitmodules
  28. .gitreview
  29. .mailmap
  30. .pydevproject
  31. .zuul.yaml
  32. BUILD
  33. COPYING
  34. INSTALL
  35. Jenkinsfile
  36. package.json
  37. README.md
  38. SUBMITTING_PATCHES
  39. version.bzl
  40. WORKSPACE
  41. yarn.lock
README.md

Gerrit Code Review

Gerrit is a code review and project management tool for Git based projects.

Build Status Maven Central

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 8 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-centos8

To run a Ubuntu 20.04 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-ubuntu20

NOTE: release is optional. Last released package of the version is installed if the release number is omitted.