Confirmed users
611
edits
Sheriffing/How To/Escalate: Difference between revisions
→Guidelines on escalating outages: add document for CI issue escalation, clean up Ciduty info
m (Update BuildDuty to CiDuty. Renaming project) |
(→Guidelines on escalating outages: add document for CI issue escalation, clean up Ciduty info) |
||
| Line 2: | Line 2: | ||
= Guidelines on escalating outages = | = Guidelines on escalating outages = | ||
== | == RelOps == | ||
Escalate infrastructure / issues with the continuous integration (CI) in #ci on IRC. [https://docs.google.com/document/d/1SqyJdJrN1fOS-TG-DGNBMGG5JUmjrJYMeyItMh0j0L0/edit List of best suited contacts] (restricted) | |||
Other signs of a global issue include: | Other signs of a global issue include: | ||
| Line 11: | Line 11: | ||
== Releng and Ciduty == | == Releng and Ciduty == | ||
If it's something RelEng can handle (or you also want them to be aware), here's the escalation path: | 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 | * Follow the escalation route at https://wiki.mozilla.org/ReleaseEngineering#Contacting_Release_Engineering | ||
== TaskCluster == | == TaskCluster == | ||
* ping in #taskcluster (see https://wiki.mozilla.org/TaskCluster for coverage in any timezone) | * ping in #taskcluster (see https://wiki.mozilla.org/TaskCluster for coverage in any timezone) | ||