Sheriffing/Job Visibility Policy: Difference between revisions

Sheriffing/Job Visibility Policy (view source)

Revision as of 17:02, 21 December 2014

237 bytes removed , 21 December 2014

Bug 1082602

Edmorley

canmove, Confirmed users

1,126

edits

@@ Line 34: / Line 34: @@
 * A mozilla-central push results in ~400 jobs. The typical OrangeFactor across all trunk trees is normally (excluding the recent spike) 3-4, ie: a failure rate of ~1%.
 * Therefore as a rough guide a new platform/testsuite must have at most a 5% per job failure rate initially, and ideally <1% longer term.
-* However, sheriffs will make the final determination of whether a job type has too many intermittent failures. This will be a based on a combination of factors including failure rate, length of time the failures have been occurring, owner interest in fixing them & whether TBPL is able to make bug suggestions.
+* However, sheriffs will make the final determination of whether a job type has too many intermittent failures. This will be a based on a combination of factors including failure rate, length of time the failures have been occurring, owner interest in fixing them & whether Treeherder is able to make bug suggestions.
 ==== Must avoid patterns known to cause non deterministic failures ====
@@ Line 92: / Line 92: @@
 == 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=Tinderboxpushlog&form_name=enter_bug&op_sys=All&product=Webtools&rep_platform=All&short_desc=Please%20unhide%20job%2Fplatform%20ZZZZZZ%20on%20TBPL&version=Trunk 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. #TODO: update this for Treeherder.
+* 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.
 == My platform/test-suite does not meet the base requirements, what now? ==
 * Your platform/test-suite will still be being run, just not shown on the default view. This model has worked well for many projects/build types (eg jetpack, xulrunner, spidermonkey).
-* To see it, append '&showall=1' to the URL ({{bug|748833}} will add a checkbox for this to the TBPL UI). #TODO: update this for Treeherder.
+* To see it, click the "show/hide hidden jobs" checkbox to the left of the quick filter input field in the Treeherder UI. ({{bug|1078081}} will add URL parameter support for this soon).
 * To filter the jobs displayed, under the 'Filters' menu use the 'job name' field (which supports regexp).
-* eg: to see both ASan & Valgrind jobs on mozilla-central (neither of which are shown by default), use: [https://tbpl.mozilla.org/?showall=1&jobname=(asan|valgrind) https://tbpl.mozilla.org/?showall=1&jobname=(asan|valgrind)]
 * For Try specifically, you can request that the job type by made non-default (ie requires explicit opt-in when using trychooser syntax, and won't be scheduled with '-u all' or similar), in order to be shown in the default view on Try - [http://hg.mozilla.org/build/buildbot-configs/file/27dff21cb799/mozilla/config.py#l332 example].