Google Git
Sign in
gerrit / gerrit / 1d6d99ffcd801a6f8a56ff9d527303473bf800a9
commit1d6d99ffcd801a6f8a56ff9d527303473bf800a9[log] [tgz]
authorPrudhvi Akhil Alahari <prudhvi.alahari@linaro.org>Mon Feb 20 14:12:54 2023 +0530
committerPrudhvi Akhil Alahari <prudhvi.alahari@linaro.org>Tue Feb 28 17:57:41 2023 +0000
tree83367308fcc0a2ee0c62363a1adf428eddeaac9e
parent06256d6690a8b2f7f2b7b71baccbedd942f4e5be [diff]
Don't limit PerThreadCache rather limit PerThreadProjectCache

Before this change, PerThreadCache has an enforcing limit of 25. The
main reason for having a limit was to restrict the number of projects
cached per thread to avoid OOM exceptions (Ic2f6e11719). By enforcing
a limit on the whole PerThreadCache for just projects use case is
effecting other use cases (such as PerThreadRefByNameCache in
I7de4e2183) of PerThreadCache.

Having a limit for number of projects stored in PerThreadCache is
needed. But as PerThreadCache is designed to be generic, that limit
must be applied to just projects use case, not the whole PerThreadCache.

Introduce PerThreadProjectCache which enforces the limit instead of
PerThreadCache. Update tests accordingly.

PerThreadCache is needed in creating a per-request ref cache using
a snapshot of RefDirectory in I174fbfdb95. This change makes it
possible to create a per-request ref cache.

Also, code-owners plugin uses PerThreadCache in a couple of places.
As one of the usage is projects specific, update code-owners plugin
to use PerThreadProjectCache post this change.

Release-Notes: skip
Change-Id: I1090446b6555296c64da1c01db39b7ac3dc6f2a3
6 files changed
tree: 83367308fcc0a2ee0c62363a1adf428eddeaac9e
  1. .settings/
  2. .ts-out/
  3. antlr3/
  4. contrib/
  5. Documentation/
  6. e2e-tests/
  7. java/
  8. javatests/
  9. lib/
  10. modules/
  11. plugins/
  12. polygerrit-ui/
  13. prolog/
  14. prologtests/
  15. proto/
  16. resources/
  17. tools/
  18. webapp/
  19. polymer-bridges
  20. .bazelignore
  21. .bazelproject
  22. .bazelrc
  23. .bazelversion
  24. .editorconfig
  25. .git-blame-ignore-revs
  26. .gitignore
  27. .gitmodules
  28. .gitreview
  29. .mailmap
  30. .pydevproject
  31. .zuul.yaml
  32. BUILD
  33. COPYING
  34. INSTALL
  35. Jenkinsfile
  36. package.json
  37. README.md
  38. SUBMITTING_PATCHES
  39. version.bzl
  40. WORKSPACE
  41. yarn.lock
README.md

Gerrit Code Review

Gerrit is a code review and project management tool for Git based projects.

Build Status Maven Central

Objective

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.

Documentation

For information about how to install and use Gerrit, refer to the documentation.

Source

Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.

Reporting bugs

Please report bugs on the issue tracker.

Contribute

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.

Getting in contact

The Developer Mailing list is repo-discuss on Google Groups.

License

Gerrit is provided under the Apache License 2.0.

Build

Install Bazel and run the following:

    git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
    cd gerrit && bazel build release

Install binary packages (Deb/Rpm)

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>]

Use pre-built Gerrit images on Docker

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.