commit | e9b6815597553a669bacaeb03e6af8bdae623ad2 | [log] [tgz] |
---|---|---|
author | Luca Milanesio <luca.milanesio@gmail.com> | Tue Aug 27 23:16:11 2019 +0100 |
committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Tue Aug 27 22:16:11 2019 +0000 |
tree | 03e51f0df80320fb2b52603775e0272319e2ca53 | |
parent | 41dcad8cc53d1c84dc0b115adf17f9bfc0595d6c [diff] |
Update git submodules * Update plugins/replication from branch 'stable-2.16' to d4981a1921e48fe76d97f7cc6107ae074879bfbe - Store replication tasks instead of ref-update events Fix the granularity of persistent events on disk by storing replication tasks rather than ref-update events. Ref-updates are triggering the replication tasks, however it is tricky to perform reference counting on the associated tasks reliably, due to all the different conditions of where a replication task can be in the replication queue. Fix a recurring issue on the persistence of ref-update events. The persisted ref-update events were either removed prematurely on the filesystem or left forever orphan even after the replication was completed on all remotes and target URLs. The problem was caused by the different granularity of the incoming ref-update events and the corresponding replication tasks queued and executed. Do not persist ref-update events anymore but include remote and target URLs at the replication tasks and persist those instead. The stored objects are replication tasks and not anymore ref-update events. Bug: Issue 11172 Change-Id: I02d8cda0a124e8e3d2b9bb01b7d44f98ba717fcd
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 7 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]
To run a Ubuntu 15.04 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.