Support per-analyzer reporting disabling and user whitelists |
|||
Issue descriptionCurrently, the Gerrit details for a project have reporting_disabled and whitelisted_groups fields to control who gets gerrit reporting and make it easier to onboard projects incrementally. In order to make onboarding new analyzers incrementally easier, we could include a similar thing in the function specification. Whether or not reporting is enabled for a particular analyzer on a particular run would then depend on some combination of the project and analyzer config. whitelisted_group and disable_reporting could be extracted to a new message type (e.g. FilteringRule). We could create an intermediary state to avoid breaking prod: (1) update config to include both FilteringRule and whitelisted/disabled info, (2) update service to accept either, (3) remove the old config. Related code search link: https://cs.chromium.org/chromium/infra/go/src/infra/tricium/api/v1/config.proto?l=120
,
Mar 15 2018
Yup, definitely a mistaken bug number. The above CL was meant for 821690 :/
,
Jun 15 2018
,
Jun 15 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Mar 15 2018