| commit | da82378313f6a0e710defff3d9b5321c0fc11afa | [log] [tgz] |
|---|---|---|
| author | Edwin Kempin <ekempin@google.com> | Wed Aug 29 22:52:54 2018 +0200 |
| committer | Edwin Kempin <ekempin@google.com> | Thu Aug 30 13:25:42 2018 +0200 |
| tree | 7f3b40333662574ff2d349e7dee7123f329f14cf | |
| parent | 99c51965a9cf3bdbd8c41fd204f4e1bc2cf88080 [diff] |
Allow clients to provide ID for tracing
This makes it easier for users to communicate the trace ID to the
Gerrit support team. E.g. users can simply use a bug ID as trace ID and
then there is no need to find the generated trace ID and post it in the
bug. This is nice because finding the generated trace ID can be tricky,
e.g. for REST calls it is returned as a response header that is only
visible with curl -v or in the browser network tooling.
This slightly changes the way how tracing is enabled:
1. REST API:
* old syntax:
a) ?trace -> enabled trace
b) ?trace=true -> enabled trace
c) ?trace=false -> disabled trace
* new syntax:
a) ?trace -> enabled trace with generated trace ID
b) ?trace=foo -> enabled trace with trace ID ‘foo’
2. Git API:
* old syntax:
a) -o trace -> enabled trace
b) -o trace=true -> enabled trace
c) -o trace=false -> disabled trace
* new syntax:
a) -o trace -> enabled trace with generated trace ID
b) -o trace=foo -> enabled trace with trace ID ‘foo’
3. SSH API:
* old syntax:
a) --trace -> enabled trace
* new syntax:
a) --trace -> enabled trace with generated trace ID
b) --trace --traceId=foo -> enabled trace with trace ID ‘foo’
c) --traceId=foo -> error, cannot use --traceId without --trace
Change-Id: I4f2c3b5748678bbdf8820463d8374b854200743a
Signed-off-by: Edwin Kempin <ekempin@google.com>
Gerrit is a code review and project management tool for Git based projects.
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.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
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.
The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recursive https://gerrit.googlesource.com/gerrit
cd gerrit && bazel build release
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>]
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.