[PSA] Chromeperf is enforcing single component on new perf issue

[Wenbin Zhang]

Hi all,

You are receiving this email because you are listed as an owner of a Chromeperf benchmark or in the contact_email of a sheriff config subscription. If you are not, please let me know and ignore the rest of the email.

Overview

Buganizer will be replacing Monorail to become the new issue tracker service. On Monorail, each issue can have an arbitrary number of components. Those component values can be from sheriff config and the benchmark definition. While on Buganizer, an issue requires exactly one component.  As part of the Buganizer migration, the issue related workflow in Chromeperf will be updated to pick one single component when creating a new issue in Buganizer. 

Proposed solution

if a component exists in sheriff config, use it; otherwise, use a general base component such as 'chromium'. (This value varies per project)

The reasons we use sheriff config:
 - Compared to the benchmark definition, the sheriff config is closely related to the regression detection and issue filing.

 - Non-telemetry tests have no benchmark definition. 

We also considered choosing components from both sources but prioritizing the one from the sheriff config. Though, this will increase the maintenance effort and cause confusion on benchmark owners as the component is likely to be overridden.

Actions:

We will start by raising warnings on the subscriptions with no component when changes are made on the sheriff config. By the end of November, we will block changes on the config if any of the subscriptions has no component.

For subscription owners: if your subscription has no 'bug_component', you will be receiving an email urging you to add one.

For benchmark owners, please be aware that the component in the @benchmark.info will be ignored. We need you to make sure the same component is listed in the subscriptions (link) you're interested in. 

Please let me know if you have any questions.

Thanks,

Wenbin