User:RyanVM/Job Visibility Policy Updates: Difference between revisions

Jump to navigation Jump to search

User:RyanVM/Job Visibility Policy Updates (view source)

Revision as of 20:00, 26 June 2015

919 bytes removed ,  26 June 2015
no edit summary
(First pass of obvious Tier 2 changes)
No edit summary
Line 6: Line 6:
Common sense will apply in cases where some of the requirements are not applicable for a particular platform/build/test type.
Common sense will apply in cases where some of the requirements are not applicable for a particular platform/build/test type.


To propose changes to this policy, please speak to the sheriffs and/or post to [https://lists.mozilla.org/listinfo/dev-platform dev.platform]. <b><big>xxxRyan: SHOULD THIS BE DEV.TREE-MANAGEMENT NOW?</big></b>
To propose changes to this policy, please speak to the sheriffs and/or post to [https://lists.mozilla.org/listinfo/dev-tree-management dev.tree-management].


==== Has an active owner ====
==== Has an active owner ====
Line 102: Line 102:
== My platform/test-suite does not meet all of the additional Tier 1 requirements, what now? ==
== My platform/test-suite does not meet all of the additional Tier 1 requirements, what now? ==
* Treeherder's UI now supports Tier 2 jobs as well. These will still be visible in the default UI. However, they do not come with the guarantee of continuous sheriff monitoring, immediate backouts, etc. If a Tier 2 job begins to fail, a bug will be filed with the suite owner notified to resolve the regression.
* Treeherder's UI now supports Tier 2 jobs as well. These will still be visible in the default UI. However, they do not come with the guarantee of continuous sheriff monitoring, immediate backouts, etc. If a Tier 2 job begins to fail, a bug will be filed with the suite owner notified to resolve the regression.
== The future ==
<b><big>xxxRyan: IS THIS ACCURATE ANYMORE?</big></b>
* Planned improvements to our tooling will likely mean that some of these requirements can be relaxed in the future, as well as making it easier for maintainers of non-default-view job types to track their success/failure without having to monitor Treeherder continuously.
* Planned features for [[Auto-tools/Projects/Treeherder]] include:
** Multiple dashboards/views for different use-cases/teams (giving us more flexibility than just "default view").
** Opt-in notifications (email, IRC, dashboard, ...?) of failures for desired job types (see proposal in {{bug|851061}}).
* [[Auto-tools/Projects/Bisect_in_the_cloud]] will allow sheriffs to more easily narrow regression ranges for job types that do not run on every push, making it more viable to accept them into certain views/dashboards.
RyanVM
Confirmed users
1,052

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1081681"

Navigation menu