Canmove, confirm
2,850
edits
Changes
→Guidelines on escalating build farm events to Release Engineering and the MOC
{{Sheriffing How To|Escalating issues to release engineering and the MOC}}
= Guidelines on escalating build farm events to Release Engineering and the MOC outages =
== MOC ==If an issue appears "global" -- outside of what RelEng can control like ftp.m.o you cannot pinpoint the affected system or hg.m.o being down -- then team responsible, going directly to the MOC can save a lot of time -- , especially during off -hours. The MOC can be reached in irc #moc. The MOC knows how to contact and escalate any issue.
Other signs of a global issue include:
* you see nagios alerts for the issue in #sysadmins
* there's already a status (https://status.mozilla.org/) (but still let MOC know it's tree-impacting)
== Releng ==
If it's something RelEng can handle (or you also want them to be aware), here's the escalation path:
* ping *|buildduty in #releng
* use the !squirrel stalk word in #releng
* 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)
