e2e-tests: Add FlushProjectsCacheThenRebuild and ListProjects scenarios

Introduce the FlushProjectsCacheThenRebuild scenario, which differs from
FlushProjectsCache (on which it is based). Make this new scenario assume
an already initialized site with multiple projects. Make it *not* create
a test project then, as opposed to the FlushProjectsCache base scenario.

However, make that new scenario rebuild the site's projects cache, once
done checking the flushing of that cache. Do so to restore the site's
ability to reliably serve all those multiple projects. Use the
list-projects (here REST) command for such a re-warmup purpose. The
requestTimeout may require an increase for that request to return an OK,
in [1] below.

These hereby introduced scenarios are meant as functional e2e test ones.
FlushProjectsCacheThenRebuild reuses ListProjects, but the latter can be
used independently of the former, as well. ListProjects is based on the
REST endpoint [2].

[1] src/test/resources/gatling.conf
[2] https://gerrit-documentation.storage.googleapis.com/Documentation/3.0.11/rest-api-projects.html#list-projects

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

Gerrit Code Review

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

Build Status

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