Confirmed users
611
edits
Sheriffing/Schedule for Tasks performed by Code Sheriffs: Difference between revisions
Jump to navigation
Jump to search
Sheriffing/Schedule for Tasks performed by Code Sheriffs (view source)
Revision as of 20:03, 26 January 2021
, 26 January 2021add release graph watching with taskcluster
(add task to increase version numbers on howto page for central-as-beta and beta-as-release simulations) |
(add release graph watching with taskcluster) |
||
| Line 1: | Line 1: | ||
Version: | Version: 7 (Last Updated 2021-01-26) | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| Line 49: | Line 49: | ||
Sometimes these beta builds are not part of the last 10 pushes which are shown by default by Treeherder. People starting a shift during which such a "release graph" for beta is supposed to run shall load pushes for mozilla-beta until they see a push with changes affecting also the US English Firefox (= usually the pushes from release management). These should get new running tasks after the aforementioned times. For the Sunday to Monday shift, this can be a push from Friday. | Sometimes these beta builds are not part of the last 10 pushes which are shown by default by Treeherder. People starting a shift during which such a "release graph" for beta is supposed to run shall load pushes for mozilla-beta until they see a push with changes affecting also the US English Firefox (= usually the pushes from release management). These should get new running tasks after the aforementioned times. For the Sunday to Monday shift, this can be a push from Friday. | ||
Failing tasks ("UV", "c-up", "L10n" etc.) should be rerun and escalated in the [https://chat.mozilla.org/#/room/#releaseduty:mozilla.org releaseduty] channel on Matrix if they continue to fail. | * Failing tasks ("UV", "c-up", "L10n" etc.) should be rerun and escalated in the [https://chat.mozilla.org/#/room/#releaseduty:mozilla.org releaseduty] channel on Matrix if they continue to fail. | ||
* 5h after the release graphs got scheduled and posted in the [https://chat.mozilla.org/#/room/#releaseduty:mozilla.org releaseduty channel] (4am Romanian time in winter, 5am in summer), check the link from the channel if all tasks completed successfully (if the requirements are fulfilled for the build to ship). | |||
** The page can slow down the browser: If you notice this, just open the page, wait for it to load the data about all the tasks belonging to the release graph, check if there are tasks which are still not complete yet, and close the page. | |||
** Not every task is shown by Treeherder but this Taskcluster view is aware of all. If there are still unexpectedly incomplete tasks 5h after the start of the release graph, mention it in the [https://chat.mozilla.org/#/room/#releaseduty:mozilla.org releaseduty channel] and create a bug if there is no reply in 15 minutes. | |||
** Be aware 2 release graphs have to be checked per beta release (the "Beta" branded one and the one for the "Developer Edition"). | |||
**The same process also applies to "rapid" releases and "ESR" releases. | |||
====Sheriffing and quality/stability related tasks executed by one person (Aryx)==== | ====Sheriffing and quality/stability related tasks executed by one person (Aryx)==== | ||