Google Git
Sign in
gerrit / gerrit.git / 4f126715f846b5c7e8c4150dfed9db3a8eb68c51
commit4f126715f846b5c7e8c4150dfed9db3a8eb68c51[log] [tgz]
authorBen Rohlfs <brohlfs@google.com>Mon Sep 04 13:04:27 2023 +0200
committerBen Rohlfs <brohlfs@google.com>Mon Sep 04 12:23:01 2023 +0000
tree19b72d45ae03e15f7657ff356c12a99502f9d3c3
parentb9093387abb5b1134a96e622a005eed6db966f41 [diff]
Fix admin links that contain the base URL twice

Change 137551 has introduced the concept of `noBaseUrl` admin links,
but in a change comment it was claimed: "The idea is for the existence
of `noBaseUrl` to be as short-lived as possible. Ideally by the end of
the week, but we'll see." Well, a couple of weeks have passed since
2017, and in the meantime the hard coded URLs were indeed fixed to
include the base URL. So there is no need to distinguish between admin
links with and without base URL anymore.

Release-Notes: Fix admin links with duplicate base URLs.
Bug: Issue 298846017
Change-Id: I92e8d77d776662f012f05afb6095958e5441568c
(cherry picked from commit eb803454ac3cc9ef0d30b751ae8d8fcc07831977)
4 files changed
tree: 19b72d45ae03e15f7657ff356c12a99502f9d3c3
  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.