Google Git
Sign in
gerrit / gerrit / 88cb17522d421054c009283ebfae4cb54b283163
commit88cb17522d421054c009283ebfae4cb54b283163[log] [tgz]
authorMartin Fick <martin.fick@linaro.org>Fri Oct 14 09:59:51 2022 -0600
committerGerrit Code Review <noreply-gerritcodereview@google.com>Fri Oct 14 15:59:51 2022 +0000
tree123b2c67558cf7f8fb57fffdba785f192b06c4e3
parenta092026d236abe372bffa561a0e9bd45eb7b96e5 [diff]
Update git submodules

* Update plugins/replication from branch 'stable-3.5'
  to c6665b860961603b38b67f28e9d84b60ccf70d50
  - Merge branch 'stable-3.4' into 'stable-3.5'
    
    * stable-3.4:
      Do not retry replication when local repository not found
      Ensure states are updated for canceled replication tasks
    
    Change-Id: Ic0e523c7c92222b49916aed7067836d4e6d2f6e7
    
  - Demote Files.list() errors when distributor is enabled
    
    Since Files.list() errors for the 'waiting' and 'running' dirs is common
    and normal when running with a multi-primary setup, demote them to
    "atFine()" level when the distributor is enabled. This avoids making the
    logs extrememly noisy during normal multi-primary operation.
    
    Change-Id: Iefc96fb79754dad9201afbc194d85194ef257198
    
  - Merge branch 'stable-3.3' into stable-3.4
    
    * origin/stable-3.3:
      Do not retry replication when local repository not found
    
    Change-Id: I6a8d0650ca24a4aac86fdafc819b028cf8864332
    
  - Do not retry replication when local repository not found
    
    When many repositories get created and deleted in a quick succession it
    may happen that a repository gets deleted before its replication task
    starts. Such replication task will keep retrying, possibly indefinitely,
    but has no chance to succeed.
    
    Another scenario where this issue can occur is when a repository gets
    created but a replica is not reachable for some time. If the repository
    gets deleted before the replica gets reachable again, the replication
    task will keep retrying but the local repository will not exist.
    
    When handling the RepositoryNotFoundException in PushOne, set the
    retrying flag to false. This ensures that this replication task is
    not retried and gets finished.
    
    Bug: Issue 15804
    Change-Id: Ia55c5ec1c961f4c2aec9ecee8056f22b436e9fda
    
  - Ensure states are updated for canceled replication tasks
    
    When using 'replication start --wait' we need
    ReplicationState.waitForReplication() to return when the task we're
    waiting on has been canceled, either through an admin action or because
    the replication distributor determined another node already completed
    it.
    
    Add a couple tests for PushAll that confirm this behavior was previously
    broken and is fixed now.
    
    Change-Id: I36320ae079af5d7673e05d20ddc94b42a9b04347
1 file changed
tree: 123b2c67558cf7f8fb57fffdba785f192b06c4e3
  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.