| commit | bb6ec305b288de5554b69d4a73ef64e2953dca79 | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Tue May 05 09:47:24 2020 +0100 |
| committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Tue May 05 08:47:24 2020 +0000 |
| tree | e363eef5e4054ba962640081e782990975fafe0f | |
| parent | ee5234ad2c5c4b5f1e4f1e4d590311a32ed5b9f1 [diff] |
Update git submodules
* Update plugins/plugin-manager from branch 'stable-3.0'
to d3b2a6eabcb641e952f253e61b927cd1f7f6e30c
- Merge branch 'stable-2.16' into stable-3.0
* stable-2.16:
Remove plugin-manager from the list of core plugins
Remove BUCK build
Remove check with hardcoded GERRIT_NEXT_VERSION
Fix core plugin name extractions without MANIFEST.MF
Backport tests from master to stable-2.16
Change-Id: I2c2aaab77090b7b7198746664542122b03fbde0e
- Remove plugin-manager from the list of core plugins
Plugin-manager wasn't a core plugin in Gerrit v2.16,
therefore it should not be expected to be included in the
release.war and returned in the list of core plugins to install.
Change-Id: I33d05851c7e4b454b132fd117017c43fcef3be01
- Remove BUCK build
Change-Id: I23e08e237431ba6fac939e0fa79a8bd2407b91aa
- Remove check with hardcoded GERRIT_NEXT_VERSION
Checking against a fixed GERRIT_NEXT_VERSION is
a very short-sighted approach, as the next version is
evolving continuously.
Fix the issue where a stable next version was
incorrectly detected as master, just because the
Gerrit versions moved on.
Bug: Issue 11264
Change-Id: I3c3c0fd5e485ec53a5cbd21ae76154a558f2bd9f
- Fix core plugin name extractions without MANIFEST.MF
When MANIFEST.MF is missing or is incomplete, extract the
plugin name by dropping the extension of the .jar file of
the plugin contained in release.war.
Change-Id: I2f89e4d3d674602e15c4e1bc281c61c9345df8c7
- Backport tests from master to stable-2.16
The master branch of the plugin-manager contains quite a few
tests: run them also on stable-2.16, so that we can have
a green build and stable over time, with proper validation in
place.
Change-Id: If9b0ba8346b5732f451485788a6c07fb3a93c487
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.