Google Git
Sign in
gerrit / gerrit / a896f7b54e2ef69639fa651b505dc9ec231c76ca
commita896f7b54e2ef69639fa651b505dc9ec231c76ca[log] [tgz]
authorAntonio Barone <syntonyze@gmail.com>Wed Nov 09 16:15:23 2022 +0000
committerAntonio Barone <syntonyze@gmail.com>Tue Nov 15 00:02:19 2022 +0100
treefb49f722cbec08d0c6489358b166320cac72b324
parent29204a923f2d8fd4b7cc56016a900cdc3258c246 [diff]
Report pack protocol errors to the client via smart-HTTP

A regression introduced by [1], caused pack protocol errors to be
reported as 500 Server errors. This is wrong because they do not
represent failures of the HTTP transport layer, but rather a failure of
the git operation itself.

As such they should be reported to the user as a 200 OK containing the
details of the failed operation.

Note: the mapping between the Exception and the HTTP status is based on
the UploadPackErrorHandler default mapping defined in jgit.

[1] https://git.eclipse.org/r/c/jgit/jgit/+/192677

Bug: Issue 16409
Release-Notes: Report pack protocol errors to the client via smart-HTTP
Change-Id: Ic3df75f81f87ad9d5a067462ee7b0eb0bb96a799
2 files changed
tree: fb49f722cbec08d0c6489358b166320cac72b324
  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.