| commit | 6e58097de69e672f53b2c12f20f6ab1683282530 | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Wed Sep 11 00:43:41 2019 +0100 |
| committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Tue Sep 10 23:43:41 2019 +0000 |
| tree | aa4905436e507a7ac7b918a2d38dd2b19eb69fe4 | |
| parent | 384e38be07450680ecfd4176c3e631034b61571c [diff] |
Update git submodules
* Update plugins/replication from branch 'stable-3.0'
to 84f695f893025152496d6c6782660cb239845db7
- Merge branch 'stable-2.16' into stable-3.0
* stable-2.16:
ReplicationIT: speedup drain replication queue tests
ReplicationIT: Remove unused variables in tests
Reformat with GJF
Option to drain the event queue before shutdown
Change-Id: I02a30f057aba348f2977c12b669c17a560d710b1
- ReplicationIT: speedup drain replication queue tests
Do not introduce artificial delays for the testing of the
replication queue drain.
Explicitly shutdown the replication config immediately
after the push operation, so that even a small 1s replication
delay is good enough to test the functionality.
Change-Id: I68caea21675875a947c2b520d265446ca2f7fe30
- ReplicationIT: Remove unused variables in tests
Change-Id: Ic652fd71748bf7899377f5e4b3ef5e3f9d7d819a
- Reformat with GJF
Change-Id: I5e476d79c33f3e2b9bb45f3f9ea0396b20072854
- Option to drain the event queue before shutdown
The node can be down for a while and the replication events could be
missing for all that time.
When the node is coming up again, the SHA1 should be then obsolete
and then effectively lost.
Allow the Gerrit administrator to avoid delaying replication events
by automatically making the shutdown of the replication queue more
graceful and wait for all in-flight replications tasks to end before
shutting down the system.
Bug: Issue 11145
Change-Id: I9d823cd64176b4987d7ba71d9a46e717d0f52b93
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.