canmove, Confirmed users
1,126
edits
Sheriffing/Job Visibility Policy: Difference between revisions
Sheriffing/Job Visibility Policy (view source)
Revision as of 21:59, 18 October 2017
, 18 October 2017→Requesting changes in visibility: Mention CCing sheriffs
(→Requesting changes in visibility: Update after Treeherder tier/visibility process changes) |
m (→Requesting changes in visibility: Mention CCing sheriffs) |
||
| Line 91: | Line 91: | ||
* To adjust the tier for a Taskcluster job, use a bug either in the Taskcluster Task Graph component, or else a component related to the type of task being adjusted, then edit the in-tree task definiton. | * To adjust the tier for a Taskcluster job, use a bug either in the Taskcluster Task Graph component, or else a component related to the type of task being adjusted, then edit the in-tree task definiton. | ||
* For legacy buildbot jobs, the tier is set via a hardcoded whitelist of job signatures. File a bug in the Treeherder Data ingestion component and follow the steps here: https://treeherder.readthedocs.io/common_tasks.html#hide-jobs-with-tiers | * For legacy buildbot jobs, the tier is set via a hardcoded whitelist of job signatures. File a bug in the Treeherder Data ingestion component and follow the steps here: https://treeherder.readthedocs.io/common_tasks.html#hide-jobs-with-tiers | ||
* CC :sheriffs when adjusting a job's tier, so they are aware of the change and can confirm the criteria have been met. | |||
== Adding a new test task, or a new test platform? == | == Adding a new test task, or a new test platform? == | ||