| commit | afb42379c4f7979a81bb98b0e1f663e031e1b0d6 | [log] [tgz] |
|---|---|---|
| author | Alvaro Vilaplana Garcia <alvaro.vilaplana@gmail.com> | Mon Feb 12 11:30:39 2024 +0000 |
| committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Mon Feb 12 11:30:39 2024 +0000 |
| tree | eae3a0bb821772faff74cdc53796ac84c2b1d95c | |
| parent | 75e02471f15fb2be77b27db075b92795df12daca [diff] |
Update git submodules
* Update plugins/delete-project from branch 'stable-3.8'
to 825dcb41a9abfc5892ef3b0f8e89b7ca25c8dfe1
- Merge branch 'stable-3.7' into stable-3.8
* stable-3.7:
ConfigurationTest: Remove flaky invalidTargetArchiveFolder test
Send project-deleted event after project deletion
Change-Id: I2ac01b00d7ce442b96a032d90b4037670e65d79a
- ConfigurationTest: Remove flaky invalidTargetArchiveFolder test
This test is failing when running gerrit test in docker image with root
user. It's also failing when remote build execution is used (BuildBuddy
provider).
It seems to rely on the fact that the exception is thrown:
java.nio.file.FileSystemException: /\\\: Operation not permitted
However when the test is executed with BuildBuddy RBE that exception is
not raised and as a consequence of that the test ends up failing. It
looks that the folder /\\\ is created in the remote executor.
While it could be fixed with:
exec_properties = {
"dockerUser": "nobody",
},
we prefer not to complicate our build toolchain and rather remove the
test.
Change-Id: I51bccdf2cb19559690d3d88bd92cf60bc28f5fcd
- Send project-deleted event after project deletion
Gerrit EventDispatcher has two types of listeners: user restricted or
unrestricted. For the restricted listeners before sending the event
Gerrit checks if user has permission to access the project. This means
that `project-deleted` event will not be delivered to the restricted
listeners because when we send the event project is already removed
so we cannot check permissions anymore.
Bug: Issue 15778
Change-Id: I86386cf8b321a2dcc8a4a8ee6f36815e5c9228a2
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.