New issue
Advanced search Search tips

Issue 718409 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Feature idea: Tricium results blocking submit

Project Member Reported by emso@chromium.org, May 4 2017

Issue description

Investigate what would be required to let Tricium results block submit. This is partly a configuration question in that there needs to be a way to mark a result as blocking, and secondly, it is an integration question, because results would need be inspected by the CQ.
 

Comment 1 by emso@chromium.org, Jun 19 2017

One possibility is to let the CQ inspect the Tricium results of the last patch set and then block on results from certain analyzers. This integration would be mainly on the CQ side, with needed data available in Gerrit or via Progress RPCs to Tricium. The Progress RPC is currently designed around a run ID, but this could be expanded.

An slightly different approach is to mark results as blocking. This would allow an analyzer to produce both blocking and non-blocking results, but it would also be more invasive in that changes to that separation would require a change to the analyzer.
Summary: Investigate the possibility of Tricium results blocking submit (was: Tricium results blocking submit)
Components: Infra>Platform>Tricium
Components: -Infra>CodeAnalysis
Labels: -Tricium
Note, we had discussed merging CQ and Tricium, making tricium analysis jobs a type of tryjob, and making it so that tryjobs can add comments to CLs.

Then, one way of addressing this would be to make it so that such tryjobs produce comments and are run as part of presubmit in CQ.
Summary: Feature idea: Tricium results blocking submit (was: Investigate the possibility of Tricium results blocking submit)

Sign in to add a comment