| commit | dbc14037496f2365f12a19bb21b1406c9d78687f | [log] [tgz] |
|---|---|---|
| author | Quinten Yearsley <qyearsley@chromium.org> | Wed Nov 21 23:07:37 2018 |
| committer | Quinten Yearsley <qyearsley@chromium.org> | Wed Nov 21 23:07:37 2018 |
| tree | 014124ee7e20649395a54f058bd99b3c64171517 | |
| parent | deebeb966eb95a0f6beb926d060fed87bae1158b [diff] |
[tricium plugin] Stop requesting updates after first update For now, we show a link to a run page instead of actual run results. To decrease the number of Progress requests, we can stop requesting once we have the run ID. Change-Id: I251b4d0e01657c59cfd01292d95e3d3213156b27 Reviewed-on: https://chromium-review.googlesource.com/c/1347411 Reviewed-by: Marc-Antoine Ruel <maruel@chromium.org> Auto-Submit: Quinten Yearsley <qyearsley@chromium.org>
Tricium is a code analysis service for Chromium. The purpose of this plugin is to integrate with the Gerrit UI, e.g. by displaying progress of analyzers.
To check out the Tricium plugin code:
git clone https://chromium.googlesource.com/infra/gerrit-plugins/tricium
The unit tests of the plugin are web-component-tester unit tests. Dependencies are specified in bower.json and can be installed by running bower install in this directory. This requires bower to be installed.
To run the tests, run wct from this directory. See wct --help for more options.
With a local static web server, such as the one provided by Polymer CLI, you can also view and tweak UI interactively.
To install the Polymer tool-set globally, run npm install -g polymer-cli.
After running polymer serve, you can view an example of how the tricium-view element appears by navigating to http://localhost:8081/components/tricium/test/example.html.
You can create a local instance of Gerrit and use this plugin in that instance.
If needed, install bazel, and then build from the Gerrit repo root with bazel build plugins/tricium.
The Gerrit repo includes a script for trying the PolyGerrit UI with a local server local plugins but with production data. See run-with-prod-data.sh.
To set up to run PolyGerrit with a local copy of the plugin, first get the Gerrit repo:
git clone --recursive https://gerrit.googlesource.com/gerrit
Then move or link the Tricium repo so it's inside the gerrit/plugins/ directory, e.g. mv tricium gerrit/plugins/.
Known issue: with a locally run PolyGerrit, you can‘t log in, which means robot comment actions (e.g. the “not useful” button) aren’t visible by default.
It's also possible to test with a local instance of Gerrit.
To do this you must set up a Gerrit test site. To build the tricium plugin in Gerrit, it is assumed that the tricium directory is iniside the gerrit plugins directory.
Then, the local site could be started with Tricium by running run-with-testsite.sh.
This plugin is configured via the tricium.config file present in the repo's refs/meta/config ref. This file uses git config format. Example:
[host] tricium = tricium-prod.appspot.com