Sheriffing/How To/Escalate: Difference between revisions
Jump to navigation
Jump to search
(→Guidelines on escalating outages: add document for CI issue escalation, clean up Ciduty info) |
m (removed google doc link because there were too many random requests for access.) |
||
| Line 3: | Line 3: | ||
== RelOps == | == RelOps == | ||
Escalate infrastructure / issues with the continuous integration (CI) in #ci on IRC. | Escalate infrastructure / issues with the continuous integration (CI) in #ci on IRC. Request list of best suited contacts from Aryx. | ||
Other signs of a global issue include: | Other signs of a global issue include: | ||
Latest revision as of 13:38, 7 July 2019
Guidelines on escalating outages
RelOps
Escalate infrastructure / issues with the continuous integration (CI) in #ci on IRC. Request list of best suited contacts from Aryx.
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 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)