commit | cfa2eb94b3240f166df6a82321de5b1756f25c69 | [log] [tgz] |
---|---|---|
author | Dmitrii Filippov <dmfilippov@google.com> | Thu Feb 09 11:05:11 2023 +0100 |
committer | Dmitrii Filippov <dmfilippov@google.com> | Mon Feb 13 10:32:14 2023 +0000 |
tree | e2a7c7c97139d9bbbbd0308b62462beb7cea2bc8 | |
parent | 7b47db0b2be5d08f5af009259a60e9f60d99ca34 [diff] |
Introduce RefUpdateContext in gerrit. Internally (in google) we need more information about why a ref is updated; this information should be available when a ref's update is written to the storage. The following 2 options were considered: 1. Explicitly pass additional information in the BatchUpdateContext. 2. Use a solution which stores information about the operation in a thread-local variable, so it can be accessed when needed. The option 1 can't be implemented without jgit modification and at the same time this change is a Gerrit-specific. So, the second options has been selected. The InMemoryRepositoryManager was updated to ensure, that open-source code provides required context. It is possible that not all updates are covered with the RefUpdateContext, but this is not a problem for our internal use-case - we will find missed coverage from logs. Note: in this change the context verification is disabled and it is enabled in the last change in the chain. Bug: Google b/261005032 Release-Notes: skip Forward-Compatible: checked Change-Id: I3ceca085cbe46e3d392fd9bbf4984a87939a9e66
Gerrit is a code review and project management tool for Git based projects.
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.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
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.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recurse-submodules https://gerrit.googlesource.com/gerrit cd gerrit && bazel build release
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>]
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.