Google Git
Sign in
gerrit / gerrit / e86ec0ca6ef8e1de719df94316886fd4b799a02a
commite86ec0ca6ef8e1de719df94316886fd4b799a02a[log] [tgz]
authorKamil Musin <kamilm@google.com>Wed Sep 18 12:39:05 2024 +0200
committerPaladox none <thomasmulhall410@yahoo.com>Wed Nov 06 19:52:53 2024 +0000
treeb59e78f01e3247507afeb05f4f8d837114706393
parent71c50e4e33c6ca1ebcd8755c3f92921ca1074b1f [diff]
Reduce concurrency on frontend tests.

Currently our tests fail when attempting to run them locally. The reason
seems to be that, when concurrency is not set 1. All concurrently
running tests, except for 1. Have document.visibilityState === "hidden"
and document.hasFocus() === False. Which leads to failures with event
handling (and for the logic that directly interacts with the
visibilityState).

This is a temporary fix, which we will hopefully be able to remove once
the underlying issue is fixed in web-test-runner (or Chrome).

Google-Bug-Id: b/365565157
Release-Notes: skip
Change-Id: Id2d5534d46cd3fae8666b7159df2b18331ef2ffd
(cherry picked from commit e895c08185c6a427273af16a446a4d9bc3cda397)
1 file changed
tree: b59e78f01e3247507afeb05f4f8d837114706393
  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. web-dev-server.config.mjs
  41. WORKSPACE
  42. 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.