Sheriffing/Schedule for Tasks performed by Code Sheriffs: Difference between revisions

Sheriffing/Schedule for Tasks performed by Code Sheriffs (view source)

2 bytes removed , 26 January 2021

m

Confirmed users

611

edits

@@ Line 53: / Line 53: @@
 * 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.
+** Not every task is shown by Treeherder but this Taskcluster view is aware of all. If there are still unexpected 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.
 *** These usually should be filed against one of the Release Engineering :: Release Automation components in Bugzilla.
 *** Needinfo the triage owner and the [[Release_Management/Release_owners|release manager who owns the release]].