| commit | 11611c4ae5f784c2c48a059b834b0a6401d5c874 | [log] [tgz] |
|---|---|---|
| author | Edwin Kempin <ekempin@google.com> | Tue Feb 21 11:37:00 2023 +0100 |
| committer | Edwin Kempin <ekempin@google.com> | Thu Feb 23 11:29:10 2023 +0100 |
| tree | 56db114270a337eea3630cf92f5bea8ddef2adc5 | |
| parent | 3b6e3288511f133719bb92f83d72b47d9ef7a38f [diff] |
BatchUpdate: Support executing ops by different users RebaseChain uses BatchUpdate to rebase the changes of a chain within a single transaction. For RebaseChain we want to support rebasing on behalf of the uploader. For this each RebaseChangeOp needs to be executed by the user that is the uploader of the change that is being rebased. Since the changes in the chain may have different uploaders, RebaseChangeOp's in the same BatchUpdate may need to be executed by different users. To make this possible we allow specifying a user when adding ops to BatchUpdate that should be used to execute the BatchUpdateOp. The user on whom's behalf an op is executed is provided via the Context. This means we need to create a new Context instance whenever an op is executed, at least if the user for an op differs from the user that was used to execute the previous op. Change updates for the same change, patch set and user are still squashed together if they are executed consecutively. This is enabled by reusing the ChangeContextImpl for a BatchUpdateOp if it has the same change and user as the previously execute BatchUpdateOp (so that ChangeContext#getUpdate can return the same ChangeUpdate instance if it is invoked multiple times for the same patch set). Release-Notes: skip Signed-off-by: Edwin Kempin <ekempin@google.com> Change-Id: I91b502171e8f08135fcee972b05faab3f901c7a1 Signed-off-by: Edwin Kempin <ekempin@google.com>
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.