Clone this repo:


  1. 1166ae0 [tricium plugin] ensure window.gapi is loaded by Marc-Antoine Ruel · 5 weeks ago master
  2. 9b2de02 [tricium plugin] Copy reworking of auth from buildbucket plugin by Quinten Yearsley · 3 months ago
  3. b960cec [tricium-plugin] Have feedback link be a button and open in new tab by Aaron Gable · 4 months ago
  4. 4cf1778 Revert "[tricium plugin] Handle concurrent _configureOAuthLibrary calls" by Quinten Yearsley · 6 months ago
  5. fdc13db [tricium plugin] Set a limit on the amount of time to request by Quinten Yearsley · 6 months ago

Tricium Plugin for Gerrit

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.


Checking out the code

To check out the Tricium plugin code:

git clone

Running the tests

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.

Previewing UI with a static server

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.

Integration testing with Gerrit

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.

Running with PolyGerrit UI and production data

The Gerrit repo includes a script for trying the PolyGerrit UI with a local server local plugins but with production data. See

To set up to run PolyGerrit with a local copy of the plugin, first get the Gerrit repo:

git clone --recursive

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.

Running a local Gerrit instance

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

Project Configuration

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:

  tricium =