Confirm
567
edits
Changes
→Guidelines on escalating outages: add document for CI issue escalation, clean up Ciduty info
= Guidelines on escalating outages =
== MOC RelOps ==If you cannot pinpoint Escalate infrastructure / issues with the affected system or team responsible, going directly to the MOC can save a lot of time, especially during off-hours. The MOC can be reached continuous integration (CI) in irc #mocci on IRC. [https://docs. The MOC knows how to contact and escalate any issuegoogle.com/document/d/1SqyJdJrN1fOS-TG-DGNBMGG5JUmjrJYMeyItMh0j0L0/edit List of best suited contacts] (restricted)
Other signs of a global issue include:
== Releng and Ciduty ==
If it's something RelEng can handle (or you also want them to be aware), here's the escalation path:
* Follow the escalation route at https://wiki.mozilla.org/ReleaseEngineering#Contacting_Release_Engineering
== TaskCluster ==
* ping in #taskcluster (see https://wiki.mozilla.org/TaskCluster for coverage in any timezone)
