NightlyCrashTriage: Difference between revisions

NightlyCrashTriage (view source)

Revision as of 15:10, 28 January 2020

208 bytes added , 28 January 2020

Updated the channel names to point to Matrix channels

Gsvelto

Confirmed users

419

edits

@@ Line 133: / Line 133: @@
 Occasionally a Nightly build is super crashy. When this happens, there are a few things to be done.
-* First, tell an appropriate person (ping in #releng or maybe #moc) so that updates can be stopped as soon as possible.
+* First, tell an appropriate person (ping in [https://chat.mozilla.org/#/room/#releng:mozilla.org #releng] so that updates can be stopped as soon as possible.
 * Then, get a tracking bug (Release Engineering :: General) filed, either by you or the person stopping the updates.
 * Then, if the regressing patch can be identified, get it backed out from mozilla-central.
-* Then, consider asking an appropriate person (via #sheriffs, #taskcluster, #releng, or the [https://mail.mozilla.org/listinfo/sheriffs sheriffs mailing list]) to "respin" Nightly, i.e. rebuild and re-release it. This takes a couple of hours, so is only worthwhile if the next day's Nightly build is still some time off.
+* Then, consider asking an appropriate person (via [https://chat.mozilla.org/#/room/#sheriffs:mozilla.org #sheriffs], [https://chat.mozilla.org/#/room/#taskcluster:mozilla.org #taskcluster], [https://chat.mozilla.org/#/room/#releng:mozilla.org #releng], or the [https://mail.mozilla.org/listinfo/sheriffs sheriffs mailing list]) to "respin" Nightly, i.e. rebuild and re-release it. This takes a couple of hours, so is only worthwhile if the next day's Nightly build is still some time off.
 * Finally, once the issue has been resolved and new Nightly builds are ready to go out to users, contact the person who froze updates in step 1 so that updates can be unfrozen.