| commit | 7c55ca449e8085415cf617f586f260df535a2ec8 | [log] [tgz] |
|---|---|---|
| author | David Pursehouse <dpursehouse@digital.ai> | Tue May 19 13:59:51 2020 +0900 |
| committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Tue May 19 04:59:51 2020 +0000 |
| tree | 8fec013e3156433cababaf74ce77353faccefe5a | |
| parent | 07a493dc8cbce5734a0bb541261d0011e6192c83 [diff] |
Update git submodules
* Update plugins/replication from branch 'master'
to 88eeb9aa1f15fcf0d891a901990efd5574fa8cf3
- Merge branch 'stable-3.1'
* stable-3.1:
Prevent persistent task listing interruptions on IOExceptions
Change-Id: Iaa7a6e354b629fac9afdb8bf18074a4662b61541
- Merge branch 'stable-3.0' into stable-3.1
* stable-3.0:
Prevent persistent task listing interruptions on IOExceptions
Change-Id: Ie03efcc94ff8001edee557a6a413233085fab1b6
- Merge branch 'stable-2.16' into stable-3.0
* stable-2.16:
Prevent persistent task listing interruptions on IOExceptions
Change-Id: Ib8bd758a3dd9c24968ec58be921c4475a7bde030
- Prevent persistent task listing interruptions on IOExceptions
When iterating over the list of persisted tasks, it is possible for an
IOException to occur while reading a specific task. Prevent this
exception from breaking out of the iteration by catching and logging the
exception inside the loop instead of outside of it.
Also improve the logging by differentiating between failures that are
severe versus potentially related to other node actions since in a
multi-master scenario with shared storage, it is common for operations
on one node to "interfere" with task listing operations on another node
without causing a malfunction. Specifically, improve the exception
handling so that the logging in these latter cases have a likely
explanation of the listing error, and do not consider these specific
filesystem errors operational errors.
Change-Id: Ia2ad431c20142ff0ce23dbace34aec837e3d8540
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 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.