| commit | 19d1f3d45d6816d6540b6bcbde97bfb2f6b24b75 | [log] [tgz] |
|---|---|---|
| author | Mark Bekhet <mark.bekhet@ericsson.com> | Wed Mar 03 13:58:21 2021 -0500 |
| committer | Mark Bekhet <bekhet.mark@gmail.com> | Mon Mar 15 19:31:53 2021 +0000 |
| tree | 8119de632ce984055569fde47c73a9d6554abfbf | |
| parent | ca644a6289ba5ef02044b26ad3c64f64f2639571 [diff] |
Apply a second filter after receiving the initial repo list Before this change, searching a repository where the prefix is similar to the name was problematic. It sent a query having two similar conditions which resolved to one condition. For example, searching for a project named f/f would send a query inname:f AND inname:f. This is problematic when listing all the related projects to the filter, which may not correspond to the user entry. Additional examples are in [1]. Before this change, if the user entered a filter containing a special character, the query sent to the backend was modified to correspond to the query language. The reason behind it being that the query language uses some special characters as operators. Therefore, the result of the output method was inaccurate and could contain extra data that are not needed by the user. This change introduces a second method that compares the filter with the output list of the fetch method. This second filter takes the original filter and compares it with each element of the resulting array from the fetch method. This ensures that the output received by the user matches their entry. With this change, users should get the same output as the old UI. [1] https://groups.google.com/u/0/g/repo-discuss/c/pfxB4_75EL0/m/dfT-nnnMAwAJ Feature: Issue 12970 Change-Id: I5078237a9648871eb59628d4669ffa0b5b42cc08
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.