Sheriffing/How To/Escalate: Difference between revisions
Jump to navigation
Jump to search
ChrisCooper (talk | contribs) m (ChrisCooper moved page Sheriffing/How:To:Escalate to Sheriffing/How To/Escalate: More intuitive naming scheme) |
ChrisCooper (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
=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 = | |||
If an issue appears "global" -- outside of what RelEng can control like ftp.m.o or hg.m.o being down -- then going directly to the MOC can save a lot of time -- especially during off hours. The MOC can be reached either in irc #moc, or at moc@mozilla.com. The MOC knows how to contact and escalate any issue. | If an issue appears "global" -- outside of what RelEng can control like ftp.m.o or hg.m.o being down -- then going directly to the MOC can save a lot of time -- especially during off hours. The MOC can be reached either in irc #moc, or at moc@mozilla.com. The MOC knows how to contact and escalate any issue. |
Revision as of 16:59, 28 July 2017
Guidelines on escalating build farm events to Release Engineering and the MOC
If an issue appears "global" -- outside of what RelEng can control like ftp.m.o or hg.m.o being down -- then going directly to the MOC can save a lot of time -- especially during off hours. The MOC can be reached either in irc #moc, or at moc@mozilla.com. The MOC knows how to contact and escalate any issue.
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
- ping in #taskcluster (see https://wiki.mozilla.org/TaskCluster for coverage in any timezone)
Other signs of a global issue include:
- you see nagios alerts for the issue in #sysadmins
- there's already a whistle pig notification (https://whistlepig.mozilla.org/) (but still let MOC know it's tree impacting)