commit | ce4e7c6609a6aaa51745350e2a6b0661793861b3 | [log] [tgz] |
---|---|---|
author | Gal Paikin <paiking@google.com> | Fri Aug 28 18:47:32 2020 +0300 |
committer | Gal Paikin <paiking@google.com> | Wed Sep 09 13:57:16 2020 +0300 |
tree | 33d43d7bf2f4a9de191cb49c7718df9e3986e1bc | |
parent | d85657b06d5e47a75c0fc943454606f9f86a762a [diff] |
Migrate all emails to send async via asyncPostUpdate Currently, postUpdate doesn't run async, and when we want to send emails asynchronously, we need to do that manually (e.g AddReviewersEmail). The goal is to make the code more clean in regard to sending emails, and also improve the performance of emails (since not all of the emails were sent async until now, only most of them). More async emails means we can return a response before actually sending the email. All other updates are not affected, and they are still invoked synchronously. Some tests were fixed, since some tests assumed emails are sent synchronously. Generally, the most significant fix for the tests is the one in FakeEmailSender#waitForEmails and methods that call it. We now wait for asyncPostUpdates to finish before we read any emails. As a follow-up it's possible to do some more cleanup. E.g, FakeEmailSender#nextMessage() is not great when emails are sent concurrently and maybe it's better not to use it. The reason it's not good is the fact that when two emails are sent roughly at the same time and async, the order of arrival for those emails is not deterministic. However, this reason is not currently relevant since the config sendemails.threadPoolSize defaults to 1 (so 2 emails can't race) in our tests. AbstractNotificationTest could also use some additional cleanup. So far, #sent in that class was changed to support concurrent sending emails (it doesn't use FakeEmailSender#nextMessage()). @SendEmailExecutor is still needed due to Id8177b374. This is now renamed to AsyncPostUpdateExecutor and is used for all async updates. Also, introduced asyncPostUpdates.threadPoolSize to override the old sendemail.threadPoolSize. The latter is marked as deprecated. We already sent some emails async, those were removed to not make a thread call another thread. Change-Id: I64a829176506ad3f36d708d63572705abf139b87
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.