podman/.github
Chris Evich 35523d560a
GHA: Auto. re-run failed cirrus-cron builds once
With a seemingly ever growing list of cirrus-cron jobs running on
release branches, there are bound to be some hiccups.  Sometimes a lot
of them.  Normally any failures require a human to eyeball the logs
and/or manually re-run the job to see if it was simply a flake.  This
doesn't take long, but can be distracting and compounds over time.

Attempt to alleviate some maintainer burden by using a new github action
workflow to perform **one** automatic re-run on any failed builds.  This
task is scheduled an hour prior to a second failure check, and generation
of notification e-mail for review.

Note: If there are no failures, due to the auto. re-run or luck, no
e-mail is generated. If this proves useful in this repo, I intend to
re-use this workflow for other repo's cirrus-cron jobs.

Signed-off-by: Chris Evich <cevich@redhat.com>
2022-11-03 13:54:39 -04:00
..
actions/check_cirrus_cron GHA: Auto. re-run failed cirrus-cron builds once 2022-11-03 13:54:39 -04:00
workflows GHA: Auto. re-run failed cirrus-cron builds once 2022-11-03 13:54:39 -04:00
dependabot.yml dependabot: add release-note-none label 2022-05-17 13:55:01 -06:00
issue-labeler.yml github: label issues based on os fix regex 2022-01-27 21:24:34 +01:00
ISSUE_TEMPLATE.md Adds brew info podman to issue template. 2022-09-30 14:30:56 -04:00
labeler.yml Enable github labeler, use for api-change 2022-09-13 07:36:45 -06:00
PULL_REQUEST_TEMPLATE.md [CI:DOCS] PodmanImage Readme touchup 2022-06-04 15:19:09 -04:00