Sheriffing/Job Visibility Policy: Difference between revisions

Add explanation for additional tier 1 requirements, attempt 2
(Add explanation for additional tier 1 requirements)
(Add explanation for additional tier 1 requirements, attempt 2)
Line 94: Line 94:
* 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=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.


== My platform/test-suite does not meet the requirements, what now? ==
== 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).
* 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, append '&showall=1' to the URL ({{bug|748833}} will add a checkbox for this to the TBPL UI). #TODO: update this for Treeherder.
Line 100: Line 100:
* 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)]
* 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].
* 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].
== My platform/test-suite does not meet the additional tier 1 requirements, what now? ==
* Once Treeherder UI changes are made, we'll be able to have tier 2 jobs shown in the default view, without them impacting sheriffing workflows. However before these changes are made, tier 2 jobs will need to either meet the requirements for tier 1 jobs, or else be hidden from the default view


== The future ==
== The future ==
canmove, Confirmed users
1,126

edits