| commit | 18b18957476f56c019e1f39ab6df445292d58f2c | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Thu Oct 27 00:06:48 2022 +0100 |
| committer | David Ostrovsky <david@ostrovsky.org> | Wed May 10 10:21:48 2023 +0200 |
| tree | 7c844b995e611271ca823aaf199d87437f52adf9 | |
| parent | 0e727a66b13e9b670365e7aab2e6179181860f1f [diff] |
Allow indexing of change numbers imported from other servers When importing repositories form other Gerrit servers, you may have change numbers that are conflicting with other existing changes created locally. The conflict is not an issue from a project's perspective because they are still unique within the same repository. However, the Change.Id is used as primary key in Lucene and therefore the imported changes would not be able to be indexed. By creating a virtual Change.Id for imported changes, the Lucene indexing works as expected and the changes are discoverable. The Gerrit's ServerIds of the changes imported from other servers are encoded in the three MSB (Most Significant Bit) of the Change number, allowing up to 64 Gerrit servers with different ServerIds to be imported, each one having up to 250M changes. The above constraints are good enough for an initial solution in Gerrit v3.7 that doesn't require any migration or reindex. The encoding of the Gerrit imported ServerIds is done using a dictionary that take the id as key and its position in the list as the encoded value. That is a simple solution that gives complete control and understanding of which change comes from where to the Gerrit admin and allows a smoother migration to a more general solution on master and the forthcoming v3.8. The normal upgrade to v3.8 typically requires an on-line reindex of the 'changes' index which will also automatically regenerate the index entries with the virtual-id, making this change fully forward-compatible. Bug: Issue 16859 Release-Notes: allow indexing of imported changes Forward-Compatible: checked Change-Id: I7b9acabb69d20ca071629257cacbd5a893e6f4a0 (cherry picked from commit 07fa83bfacc1a42e9a079666bf17393e10a9b514)
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.