Google Git
Sign in
gerrit / gerrit / cdf4972b680840aa86104149f3638170a2ccde49
commitcdf4972b680840aa86104149f3638170a2ccde49[log] [tgz]
authorMarcin Czech <maczech@gmail.com>Fri Jun 30 22:09:01 2023 +0200
committerMarcin Czech <maczech@gmail.com>Mon Jul 10 21:45:52 2023 +0200
treedb1926aa4b237ec8e8e3a3a2af7b06ac2c874c1f
parentf4c78d9f6bb318e4b8acac9cb6b9e80dba820a54 [diff]
Preserve refs order in the GitBatchRefUpdateEvent event

Change I79eefbee introduced the concept of the single event
representing batch ref update. However this new event doesn't
preserve original order of the updated refs. This impacts event
consumers behaviour and can cause failures. For example if meta
ref is processed before patchset ref indexing operation will
fail because of the missing patchset.

To make sure that refs order is preserved and backward compatibility
is kept use LinkedHashSet instead of HashSet.

Bug: Issue 289321387
Release-Notes: Preserve refs order in the GitBatchRefUpdateEvent event
Change-Id: I198d60bb172edbccce739054da93e9f014c02c2b
2 files changed
tree: db1926aa4b237ec8e8e3a3a2af7b06ac2c874c1f
  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.