diff options
| author | Chris Evich <cevich@redhat.com> | 2022-04-11 15:30:15 -0400 |
|---|---|---|
| committer | Chris Evich <cevich@redhat.com> | 2022-04-11 15:30:15 -0400 |
| commit | 61cf2228826aab06c3179c83ebc96b58996b133f (patch) | |
| tree | 552d64d56149ed2b4467796a49cd0b50ca0ee8a9 /docs/source/markdown/podman-pod-stop.1.md | |
| parent | 1d01815c107c91f6cfe98446d334c94a97d11080 (diff) | |
| download | podman-61cf2228826aab06c3179c83ebc96b58996b133f.tar.gz podman-61cf2228826aab06c3179c83ebc96b58996b133f.tar.bz2 podman-61cf2228826aab06c3179c83ebc96b58996b133f.zip | |
Cirrus: Fix unsupported cirrus-cron build status
Every weekday when the `check_cirrus_cron` github-actions
workflow runs. It checks the status of all cirrus-cron jobs. If a build
is found with a 'FAILED' status, it triggers an alert e-mail to be sent.
However, the `test_image_build` is marked as a manually-triggered,
resulting in a perpetual status of 'EXECUTING', even if there were
failures. Fix this by only allowing the problematic task to run in pull
requests without the `[CI:DOCS]` magic keyword.
Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'docs/source/markdown/podman-pod-stop.1.md')
0 files changed, 0 insertions, 0 deletions