| commit | 1c31b0d4e58519d1a79a3e5c99775f519a117af0 | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Fri Nov 26 17:32:03 2021 +0000 |
| committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Fri Nov 26 17:32:03 2021 +0000 |
| tree | 01e1d0460020794b1c206ee59446c4bb0e4d38ed | |
| parent | 669afbefa9fe21fef97b69b5fbb0d8ce89615656 [diff] |
Update git submodules
* Update plugins/replication from branch 'master'
to 4f5de60081d7c098d09c842e3ea9d5bc920df71b
- Merge branch 'stable-3.4'
* stable-3.4:
Doc: make explicit that remoteNameStyle is for non-Gerrit repos
Doc: remoteNameStyle might result in a repo name clashes
Change-Id: I77b698b5976dda82160ca967ce52e510791e651f
- Merge branch 'stable-3.3' into stable-3.4
* stable-3.3:
Doc: make explicit that remoteNameStyle is for non-Gerrit repos
Doc: remoteNameStyle might result in a repo name clashes
Change-Id: I1b2e9c5fd408b8f8bd1a3ef3104182c6f6474559
- Merge branch 'stable-3.2' into stable-3.3
* stable-3.2:
Doc: make explicit that remoteNameStyle is for non-Gerrit repos
Doc: remoteNameStyle might result in a repo name clashes
Change-Id: I32d598a36fe20c469528eca8d4c10d8775f7a3c4
- Merge "Doc: remoteNameStyle might result in a repo name clashes" into stable-3.2
- Doc: make explicit that remoteNameStyle is for non-Gerrit repos
The documentation already specify non-Gerrit examples of use
of remoteNameStyle; however, it does not say that if the remote
repository is backed by Gerrit, the *ONLY* supported option is
"slashes", otherwise the consequences could be catastrophic.
Two Gerrit servers (e.g. primary and replica) need to have
full alignment of repository names, as they are also referenced
in the inherited ACLs. Having a repository name mapping, may
disrupt the ACLs evaluation and make the remote Gerrit replica
unusable.
Bug: Issue 15318
Change-Id: I4d9447a4d0366a98037470c0cceda36f7a1b8a25
- Doc: remoteNameStyle might result in a repo name clashes
When using the remoteNameStyle in the replication.config settings
the Gerrit admin needs to be warned on the risks of using sytles
that may be ambiguous and associate two source repositories to
the same target repository on the replica.
Example: set remoteNameStyle to basenameOnly
/foo/my-repo.git => pushed to my-repo
/bar/my-repo.git => pushed to my-repo
When two commits are pushed to the same branch on the two repos
/foo/my-repo.git and /bar/my-repo.git, the replication plugin
would push them to the same target repo my-repo, causing clashes
and losing commits (depending which one is pushed first).
The risk needs to be highlighted so that the Gerrit admin
can check that univocity of the mapping is respected.
Bug: Issue 15315
Change-Id: Iba42907bceb8d1c27d739f3b0cded4a1d7400686
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.