summaryrefslogtreecommitdiff
path: root/contrib/cirrus/cron-fail_addrs.csv
diff options
context:
space:
mode:
authorChris Evich <cevich@redhat.com>2020-10-07 16:43:36 -0400
committerChris Evich <cevich@redhat.com>2020-11-18 15:34:01 -0500
commit887f88c490a63e759a34eaf642a4eb47e8087512 (patch)
tree615ca61a428cae6deade313ced9b46a471538827 /contrib/cirrus/cron-fail_addrs.csv
parent4434bd797842c3015c0e6132eaf2509fed370c26 (diff)
downloadpodman-887f88c490a63e759a34eaf642a4eb47e8087512.tar.gz
podman-887f88c490a63e759a34eaf642a4eb47e8087512.tar.bz2
podman-887f88c490a63e759a34eaf642a4eb47e8087512.zip
Github-Actions: Send e-mail on Cirrus cron failure
This repository has a number of automaticly triggered branch-level testing enabled. However, other than remembering to go look at a specific WebUI, there is no way for anybody to notice if/when these jobs fail. This commit introduces a github-action workflow which runs periodically, checking for failed cron-triggered Cirrus-CI jobs. When it finds any, it formats a simple report for e-mail delivery. The list of destination addresses is configurable at any time by merging changes to a simple CSV file. Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'contrib/cirrus/cron-fail_addrs.csv')
-rw-r--r--contrib/cirrus/cron-fail_addrs.csv1
1 files changed, 1 insertions, 0 deletions
diff --git a/contrib/cirrus/cron-fail_addrs.csv b/contrib/cirrus/cron-fail_addrs.csv
new file mode 100644
index 000000000..c25fc1226
--- /dev/null
+++ b/contrib/cirrus/cron-fail_addrs.csv
@@ -0,0 +1 @@
+rh.container.bot@gmail.com