commit | d741a4afb795019d8b252b36289977e48f44dcee | [log] [tgz] |
---|---|---|
author | Edwin Kempin <ekempin@google.com> | Fri Dec 08 13:57:26 2017 +0100 |
committer | Edwin Kempin <ekempin@google.com> | Mon Dec 18 17:12:18 2017 +0100 |
tree | 25d4f17aeda42f3f500ce682eade922102dd6a88 | |
parent | 350e3e263f2991cd1bd36207d2d56ea78482df80 [diff] |
Add an InternalAccountUpdate class to prepare updates to accounts Instead of doing account updates directly on the Account instance have an InternalAccountUpdate class with a builder for preparing account updates. This is done for the following reasons: 1. More consistency with how group updates are done (group updates are prepared with an InternalGroupUpdate class). 2. It's a preparation to make updates of different account data types atomic (e.g. update of account properties and external IDs should become atomic). 3. This change will allow us to replace the Account entity class from ReviewDb times with an AutoValue type (similar to how groups are represented by the InternalGroup AutoValue type). To achieve 2. the new InternalAccountUpdate class can be extended to host updates for further account data like external IDs, preferences etc. Since all account data is stored in the All-Users repository the updates in NoteDb can be atomic across different account data types. In particular this will simplify the account creation which first creates the external ID and then inserts the account, but then has to rollback the external ID creation if the account insertion fails. In contrast to GroupsUpdate AccountsUpdate continues to require a consumer for updates (instead of an InternalAccountUpdate instance). This is because some callers of the AccountsUpdate class need to have access to the loaded account to decide which updates should be done (e.g. ReceiveCommits wants to set a full name only if a full name wasn't set yet). This is why the consumer is invoked with a new AccountUpdate that provides both, access to the current account (for reading) and access to the InternalAccountUpdate builder (for updates). Change-Id: I057361b9ca4d3a61475c77a6ff06f40ebedaec0f 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 IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
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 --recursive 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 7 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]
To run a Ubuntu 15.04 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.