d7bdc5e855
* Update plugins/replication from branch 'master'
to 0f76d57321863a8b49a27d4c550148214be059dc
- Merge branch 'stable-3.3'
* stable-3.3:
Remove dependency on commons-io library
Fix replication to retry on lock errors
Change-Id: I52fea645ccb55c1380702c071f1c7f7f134dc1b2
- Merge branch 'stable-3.2' into stable-3.3
* stable-3.2:
Fix replication to retry on lock errors
Change-Id: Iab364714135d693e011e8abbf7782ae620d009c4
- Merge branch 'stable-3.1' into stable-3.2
* stable-3.1:
Fix replication to retry on lock errors
Change-Id: Icacd9095feaefd240803405c5b0a16cc0b3a9ed8
- Merge branch 'stable-3.0' into stable-3.1
* stable-3.0:
Fix replication to retry on lock errors
Change-Id: Ib4b2c1fcac5da6551f72bce68a101b93e9b43b19
- Merge branch 'stable-2.16' into stable-3.0
* stable-2.16:
Fix replication to retry on lock errors
Change-Id: I6e262d2c22d2dcd49b341b3c752d6d8b6c93b32c
- Remove dependency on commons-io library
This dependency was added in Id12780948a4 to support remoteNameStyle
"basenameOnly". The only reason for this dependency is to translate
project name from "foo/bar/myrepo" to myrepo.
It seems to be overkill to add 169 KB to the plugin distribution
for one single method.
Another disadvantage is that the version of common-io library used
for this is 2.2 from 2012. If gerrit installation site is using some
other plugins in addition to replication plugin, then it can easily
lead to classpath collision, when different versions of commons-io
libraries are included as transitive dependencies of different plugins.
To rectify, use a replacement method from guava library.
Change-Id: Id254dc38831832a9855bd204e4c2129ec64b88ae
- Fix replication to retry on lock errors
Versions of Git released since 2014 have created a new status
"failed to update ref" which replaces the two statuses "failed to lock"
and "failed to write". So, we now see the newer status when the remote
is unable to lock a ref.
Refer Git commit:
6629ea2d4a
Config 'lockErrorMaxRetries' is not removed as part of this change
as folks who have it configured currently don't run into unexpected
behavior with retries when they upgrade to a newer version of the
plugin. Also, the "failed to lock" check is not removed for folks
still using a version of Git older than 2014.
Change-Id: I9b3b15bebd55df30cbee50a0e0c2190d04f2f443
Gerrit Code Review
Gerrit is a code review and project management tool for Git based projects.
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.