| commit | 92b85cb4c4951f320645e8eae486e02aa46dcbb5 | [log] [tgz] |
|---|---|---|
| author | Edwin Kempin <ekempin@google.com> | Tue Aug 08 14:47:25 2023 +0000 |
| committer | Edwin Kempin <ekempin@google.com> | Wed Aug 09 10:55:39 2023 +0000 |
| tree | 0bf1fd23a9229967c6eead5d0863a5d09d0d737b | |
| parent | 7a1849f3e4aea612946dcc8afc5254def175b3ee [diff] |
Add interface for ListProjects REST endpoint ListProjects is a legacy REST endpoint that was used to list/query projects before we had a project index, but it's still widely used (e.g. from the ls-projects SSH command or from Gerrit's web frontend to populate the repository list). With QueryProjects we have a REST endpoint that uses the project index for querying projects which should be used instead, but it doesn't support all functionality of the ListProject REST endpoint. At Google we want to deprecate most of the options that the ListProjects REST endpoint supports so that ListProjects can delegate all requests to QueryProjects. Doing this is a backwards incompatible change which will break the REST API and the SSH API for listing projects. This is an API that is known to have lots of usage by automation tools and hence breaking this API for everyone is not an option. By adding an interface for ListProjects we can replace the REST endpoint implementation internally at Google, so that this breakage only affects Google, but no one else. Unfortunately it's not possible to apply @Option annotations on the interface methods. To avoid that all implementations need to define the options by themselves we add an AbstractListProjects implementation that defines the options and that can be extended by ListProjects implementations. The ListProjects interface is used everywhere where projects need to be listed, except from the ls-projects SSH command which has special needs. This is fine for us (Google) since we are not using SSH. Dynamic options beans need to be bound on the ListProjects implementation class. Release-Notes: skip Bug: Google b/289490702 Change-Id: Ibf963cf3db7e02af1996e13bf59a67c38a182e2a 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 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.