Sheriffing: Difference between revisions
Jump to navigation
Jump to search
(Move list of sheriffs here from Tree_Rules/Integration#Meet_the_Sheriffs and add link to modules page instead of repeating here) |
m (IRC > Matrix) |
||
| (26 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
= The Tree Sheriffs = | = The Tree Sheriffs, aka Code Sheriffs = | ||
When Mozilla moved to the "inbound" model of tree management, the Tree Sheriffs became important stewards of our engineering infrastructure. The primary responsibility of the Sheriffs is to aid developers to easily, quickly, and seamlessly land their code in the proper location(s) and ensure that code does not break our automated tests. In the service of this objective, the Sheriffs work closely with the larger engineering organization to create and enforce landing policies that increase productivity while maintaining an efficient and robust automated testing system. Beyond the policy role, they have also become shepherds of automation quality by monitoring intermittent failures, performing uplifts and merges, and identifying poorly performing automation machines. A formal module for the Tree Sheriffs in the larger context of the Activities Module was created: [[Modules/Activities#Tree_Sheriffs]]. | |||
When | |||
== Meet the Sheriffs == | == Meet the Sheriffs == | ||
The owners & peers of the Tree Sheriffs module can be found on the [[Modules/Activities#Tree_Sheriffs|module page]], however for day-to-day sheriffduty coverage, look for the following people in #developers and #sheriffs. The on-duty sheriffs will typically have "|sheriffduty" appended to their Matrix nick. | |||
* UTC+2: 15 sheriffs from SoftVision in Romania on a rotating schedule | |||
* UTC+1: Sebastian Hengst [:Aryx] (staff/community) | |||
* UTC-8: Phil Ringnalda [:philor] (community) | |||
We're always looking for more people to join the community team and help out - just drop us a message in the [https://chat.mozilla.org/#/room/#sheriffs:mozilla.org sheriffs] Matrix channel or at the [https://mail.mozilla.org/listinfo/sheriffs sheriffs mailing list]! | |||
https:// | |||
= Links = | = Links = | ||
== For Developers == | |||
* [https://developer.mozilla.org/en-US/docs/Developer_Guide/Committing_Rules_and_Responsibilities Committing rules and responsibilities] | * [https://developer.mozilla.org/en-US/docs/Developer_Guide/Committing_Rules_and_Responsibilities Committing rules and responsibilities] | ||
* [[Tree Rules]] | * [[Tree Rules]] | ||
* | * [[Sheriffing/How_To/Recommended_Try_Practices|Recommended Try Practices]] | ||
* [[Sheriffing/How: | |||
* [[Sheriffing/How | == For Sheriffs == | ||
* [[Sheriffing/How To/Getting_started_as_a_sheriff|How to get started as a sheriff]] | |||
* [[Sheriffing/Job Visibility Policy]] | * [[:Category:Sheriffing_How_To|How-to guides]] | ||
* [[Sheriffing/ | * [[Sheriffing/How To/Treeherder|Treeherder]]: how to interpret Treeherder data. Also explains how to [[Sheriffing/How_To/Treeherder#Classifying.2FStarring_jobs|star failures]]. | ||
* [[ | ** [[Sheriffing/Job Visibility Policy|Job Visibility Policy]] | ||
* | ** [[Sheriffing/Test_Disabling_Policy|Test Disabling Policy]] | ||
* | * [[Sheriffing/Deciding To Close A Tree|Deciding To Close A Tree]] | ||
* [[Sheriffing/Schedule for Tasks performed by Code Sheriffs|Schedule for Tasks performed by Code Sheriffs]] | |||
* [https://docs.google.com/document/d/1EkSwx8QanwMw88KFOQjiKKtu6HWNrQDoDSIy41v3ELE/edit# Uplift simulation reference]: a list of all beta uplift simulations performed and associated bugs filed | |||
Latest revision as of 10:29, 13 September 2020
The Tree Sheriffs, aka Code Sheriffs
When Mozilla moved to the "inbound" model of tree management, the Tree Sheriffs became important stewards of our engineering infrastructure. The primary responsibility of the Sheriffs is to aid developers to easily, quickly, and seamlessly land their code in the proper location(s) and ensure that code does not break our automated tests. In the service of this objective, the Sheriffs work closely with the larger engineering organization to create and enforce landing policies that increase productivity while maintaining an efficient and robust automated testing system. Beyond the policy role, they have also become shepherds of automation quality by monitoring intermittent failures, performing uplifts and merges, and identifying poorly performing automation machines. A formal module for the Tree Sheriffs in the larger context of the Activities Module was created: Modules/Activities#Tree_Sheriffs.
Meet the Sheriffs
The owners & peers of the Tree Sheriffs module can be found on the module page, however for day-to-day sheriffduty coverage, look for the following people in #developers and #sheriffs. The on-duty sheriffs will typically have "|sheriffduty" appended to their Matrix nick.
- UTC+2: 15 sheriffs from SoftVision in Romania on a rotating schedule
- UTC+1: Sebastian Hengst [:Aryx] (staff/community)
- UTC-8: Phil Ringnalda [:philor] (community)
We're always looking for more people to join the community team and help out - just drop us a message in the sheriffs Matrix channel or at the sheriffs mailing list!
Links
For Developers
For Sheriffs
- How to get started as a sheriff
- How-to guides
- Treeherder: how to interpret Treeherder data. Also explains how to star failures.
- Deciding To Close A Tree
- Schedule for Tasks performed by Code Sheriffs
- Uplift simulation reference: a list of all beta uplift simulations performed and associated bugs filed