Sheriffing/Job Visibility Policy: Difference between revisions

Sheriffing/Job Visibility Policy (view source)

81 bytes removed , 18 October 2017

→‎Requesting changes in visibility: Update after Treeherder tier/visibility process changes

canmove, Confirmed users

1,126

edits

@@ Line 88: / Line 88: @@
 == Requesting changes in visibility ==
-* Please file a bug using this [https://bugzilla.mozilla.org/enter_bug.cgi?cc=sheriffs%40mozilla.bugs&comment=Job%2Fplatform%20ZZZZZZ%20now%20meets%20the%20requirements%20at%3A%0D%0Ahttps%3A%2F%2Fwiki.mozilla.org%2FSheriffing%2FJob_Visibility_Policy%0D%0A%0D%0APlease%20may%20it%20be%20unhidden&component=Treeherder&op_sys=All&product=Tree+Management&rep_platform=All&short_desc=Please%20unhide%20job%2Fplatform%20ZZZZZZ%20on%20Treeherder template], so that changes in visibility are more discoverable (vs IRC or asking as part of a bug in another product/component) and reasoning/history is preserved.
+* Jobs that are marked as tier 3 will be hidden in Treeherder by default.
+* 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
 == Adding a new test task, or a new test platform? ==
 * Be sure to demonstrate an acceptable intermittent failure rate for your new test tasks on try, and include the try links in the bug which adds the new tasks. Usually that means repeating each new test task at least 10 times (try: --rebuild 10).