governance: noting CI is a maintainer responsibility, emailing failur…

…es to on-call (envoyproxy#6342) Signed-off-by: Alyssa Wilk <[email protected]>
veshij · Mar 21, 2019 · 9a2cd6b · 9a2cd6b
1 parent 2b74ebf
commit 9a2cd6b
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 0 deletions.
diff --git a/.circleci/config.yml b/.circleci/config.yml
@@ -215,3 +215,10 @@ workflows:
             tags:
               only: /^v.*/
       - mac
+
+# Instructions from https://docs.opsgenie.com/docs/circleci-integration
+# Configuration at https://app.opsgenie.com/integration#/edit/CircleCi/d9585dd7-b9c5-4723-abee-647a623639e4
+# Deletion possible via https://app.opsgenie.com/integration#/configured-integrations
+notify:
+  webhooks:
+     -url: https://api.opsgenie.com/v1/json/circleci?apiKey=f45d58a7-15a4-4800-8d2c-f460ec02cf71
diff --git a/GOVERNANCE.md b/GOVERNANCE.md
@@ -37,6 +37,8 @@
 * Triage GitHub issues and perform pull request reviews for other maintainers and the community.
   The areas of specialization listed in [OWNERS.md](OWNERS.md) can be used to help with routing
   an issue/question to the right person.
+* Triage build issues - file issues for known flaky builds or bugs, and either fix or find someone
+  to fix any master build breakages.
 * During GitHub issue triage, apply all applicable [labels](https://github.com/envoyproxy/envoy/labels)
   to each new issue. Labels are extremely useful for future issue follow up. Which labels to apply
   is somewhat subjective so just use your best judgment. A few of the most important labels that are