Update git submodules
* Update plugins/replication from branch 'master'
to 78b8b36a90a36c0db91df06aea0c78114a03a1ef
- Merge branch 'stable-3.14'
* stable-3.14:
Ignore files not named by a sha1 in the replication task storage
Name url distribution by the reason it is asked
Change-Id: Ie1e0074304004cdc5569ebe6b3189e3735e48b4d
- Merge branch 'stable-3.13' into stable-3.14
* stable-3.13:
Ignore files not named by a sha1 in the replication task storage
Name url distribution by the reason it is asked
Change-Id: Ib71f96dba7b1e30ec60133e1b538e34ad9f67bbe
- Merge branch 'stable-3.12' into stable-3.13
* stable-3.12:
Ignore files not named by a sha1 in the replication task storage
Name url distribution by the reason it is asked
Change-Id: I04e5180c6df46a8311f182119a35580917ed1aa1
- Merge branch 'stable-3.11' into stable-3.12
* stable-3.11:
Ignore files not named by a sha1 in the replication task storage
Name url distribution by the reason it is asked
Change-Id: I56f616c5d58e37ddee5767cc23836cac07c52e72
- Merge "Ignore files not named by a sha1 in the replication task storage" into stable-3.11
- Ignore files not named by a sha1 in the replication task storage
On NFS, deleting or renaming a file that a process on the same client
still has open turns it into a hidden ".nfsXXXX" file, which the client
removes once the process closes it. If the process dies first, the file
stays behind for good. With several primaries sharing the task storage,
this can happen to a task file that a primary is reading while it starts
or finishes the same task.
ReplicationTasksStorage listed such a file as a task, keyed by its file
name instead of the sha1 of the task. With the replication distributor
enabled this loops forever: every distribution cycle replays the file,
the resulting push cannot match the stored task by sha1, so it is pruned
as externally completed and scheduled again on the next cycle, on every
primary. The push never runs, since starting it renames the file named
after the sha1, which does not exist. For an ..all.. task this schedules
and cancels a full push of the project every few seconds, for as long as
the file exists.
Task files are always named after the sha1 of their task, so skip files
whose name is not a sha1 when walking the storage. This also covers other
stray files, such as editor or rsync leftovers.
Release-Notes: Ignore files not named by a sha1, such as NFS ".nfsXXXX" files, in the replication task storage, which the distributor kept rescheduling forever
Change-Id: I907be49b01103f11e483f8afdd2b6f2d983432fd
- Name url distribution by the reason it is asked
`Instance.select` answered for every caller: pushing refs, creating a
project, updating its HEAD and deleting it all asked the same question,
so a reader had to follow the call sites to see which policy applied,
and a strategy could not treat one of them differently. Replace it with
`urlsToReplicateTo`, `urlsToCreateOn` and `urlsToDeleteFrom`, the
reasons the plugin asks for, and let creating and deleting default to
the URLs a project is replicated to, which is where it was written. A
HEAD update replicates a ref like any other, so it keeps following
`urlsToReplicateTo`.
No strategy answers them differently yet, so behaviour is unchanged:
`all` keeps creating on and deleting from every URL, `roundRobin` one
URL at a time and `projectSharded` the URL owning the project. Whether
those are the right policies can now be decided per reason, and in this
class rather than in its callers.
Change-Id: Ib793439e85e3b7c5c40432965b8aa2c22b5cb42e
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.
Due to spam abuse, membership in the repo-discuss Google Group is required in order to create issues. See the announcement for more info.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Due to spam abuse, membership in the repo-discuss Google Group is required in order to create Gerrit changes on the gerrit-review Gerrit server.
Note that we do not accept Pull Requests via the GitHub mirror.
Find a full list of contact options on the website.
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.