Google Git
Sign in
gerrit / gerrit / 3abd6774df91bc27740af76bb576bd7c6611a507
commit3abd6774df91bc27740af76bb576bd7c6611a507[log] [tgz]
authorNasser Grainawi <nasser.grainawi@linaro.org>Mon Jul 29 15:36:03 2024 -0600
committerGerrit Code Review <noreply-gerritcodereview@google.com>Mon Jul 29 21:36:03 2024 +0000
tree9554592af79e49e31f4195d4d42189a822deab90
parent5a6d436bbb18a31534a0e0820fce04bc4ceb6d47 [diff]
Update git submodules

* Update plugins/replication from branch 'stable-3.8'
  to 584aea1a8968a9162d78460422a285a87910f502
  - Merge branch 'stable-3.5' into stable-3.8
    
    * stable-3.5:
      TasksStorage: Remove synchronized from methods
      Place the replaying flag clearing in a finally
      Demote delete errors when distributor is enabled
      distributor: Reduce log level for no-op consolidations
    
    Change-Id: Iaa6d4a59d5cb26879500f2d36852eaa30efc5d7b
    Release-Notes: skip
    
  - TasksStorage: Remove synchronized from methods
    
    These aren't expected to be necessary for correctness.
    
    Change-Id: Id23d3b385e289ba453638b76d6523016a5aabf2a
    
  - Place the replaying flag clearing in a finally
    
    This ensure that 'replaying' will be set to false even if an exception
    occurs in pruneNoLongerPending(), otherwise if would be possible for the
    distributor to get "stuck" and never be able to run again.
    
    Release-Notes: Avoid opportunity to inadvertently block the distributor
    Change-Id: I4628a574ad54ca6abd591138edc48e12a39447e7
    
  - Demote delete errors when distributor is enabled
    
    Since delete errors for Tasks is expected after recovery (when another
    nodes starts up) when running with a multi-primary setup, demote them to
    "atFine()" level when the distributor is enabled. This avoids errors in
    the logs during normal multi-primary operation.
    
    Release-Notes: Reduced log level for Task deletion errors in MP setups
    Change-Id: Iccca2e1bd2b91b91e12a14c4e473c8a6df6fd4b7
    
  - distributor: Reduce log level for no-op consolidations
    
    It's expected that the replication distributor will generate many of
    these log messages on a busy instance because it will repeatedly
    re-schedule the same ref updates. Since those messages likely aren't
    operationally interesting, reduce the log level to atFine when
    scheduling is happening based on stored replication tasks and the ref is
    already scheduled in the push task.
    
    Change-Id: I07d071af848481fa84e1ba26fb8287c5e61d1d67
    Release-Notes: Reduced log level for no-op distributor push consolidations
1 file changed
tree: 9554592af79e49e31f4195d4d42189a822deab90
  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. web-dev-server.config.mjs
  41. WORKSPACE
  42. 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.