commit | 756f561ecf177c00682127ab80a0846f109ccb0c | [log] [tgz] |
---|---|---|
author | Gal Paikin <paiking@google.com> | Tue Jun 08 13:38:00 2021 +0200 |
committer | Gal Paikin <paiking@google.com> | Wed Jun 09 10:27:57 2021 +0200 |
tree | e2c37c162809e2c00419e381322d8536aba7e6a4 | |
parent | 0c4d819947a56b656af19eb167bc866dd36c9923 [diff] |
Return X-Gerrit-UpdatedRef in the response headers of WRITE requests For each REST-API request, we can track which refs were changed via GitReferenceUpdatedListener which is already used and tested by the plugins, caches, and indices. Using the information of which refs were changed, for each request that changed any of the refs, we return the changed refs in the response header of `X-Gerrit-UpdatedRef` in the format: REPONAME~REFNAME~OLD_SHA-1~NEW_SHA-1. This is useful because: 1. Successful operations on changes are signaled by an update on the meta ref (and similarly for other operations such as updating accounts signaled by update to the account ref). 2. Returning the SHA-1s generically in the response headers can reduce load on Gerrit: users will not have to call Gerrit to get this information since Gerrit already always returns it. For example, some users need the new SHA-1 of the destination branch, which we don't return on submission, and right now they are forced to call Gerrit again after submission to retrieve the SHA-1. 3. Because of (2), for multi-site setups, we are not impacted by replication lags that could be caused by the users calling Gerrit more times than they really need. While at it, we change WebSession to be an abstract class instead of an interface to have ref updates as part of the class. Change-Id: Iaac3bf1036408c7f0b2d48494b544032c76c5462
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.