1
0
mirror of https://github.com/containers/netavark.git synced 2026-02-05 15:45:47 +01:00

14 Commits

Author SHA1 Message Date
renovate[bot]
1b53849b8c [skip-ci] Update GitHub Artifact Actions
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2025-12-12 23:07:01 +00:00
renovate[bot]
6c2066a3fc [skip-ci] Update actions/checkout action to v6
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2025-11-20 17:26:21 +00:00
Paul Holzinger
cd8d1bf787 fix download artifact action
The v5 update broke the download location, it seems to extarct to the
root now and no longer into the release-artifacts directory. So fix this
by specifying the path explicitly, see
https://github.com/actions/download-artifact/issues/419.

Fixes: #1312

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
2025-11-05 15:21:33 +01:00
renovate[bot]
0f3b790593 [skip-ci] Update GitHub Artifact Actions
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2025-10-24 22:01:01 +00:00
Paul Holzinger
b31bc38ff3 Revert "[skip-ci] Update actions/download-artifact action to v5"
This reverts commit 9b3e3328f2.

The action is broken as the file layout changed, see #1312.

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
2025-08-20 16:07:04 +02:00
renovate[bot]
e6ef79ef63 [skip-ci] Update actions/checkout action to v5
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2025-08-11 14:21:40 +00:00
renovate[bot]
9b3e3328f2 [skip-ci] Update actions/download-artifact action to v5
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2025-08-06 02:22:55 +00:00
Paul Holzinger
ea3479b53b .github: check_cirrus_cron work around github bug
So I wondered why our email workflow only reported things for podman...

It seems the secrets: inherit is broken and no longer working, I see all
jobs on all repos failing with:

Error when evaluating 'secrets'. .github/workflows/check_cirrus_cron.yml (Line: 19, Col: 11): Secret SECRET_CIRRUS_API_KEY is required, but not provided while calling.

This makes no sense to me I doubled checked the names, nothing changed
on our side and it is consistent for all projects. Interestingly this
same thing passed on March 10 and 11 (on all repos) but failed before
and after this as well.

Per[1] we are not alone, anyway let's try to get this working again even
if it means more duplication.

[1] actions/runner#2709

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
2025-04-11 18:54:52 +02:00
Ashley Cui
3bfe78ed76 Release GHA: Automatically publish crate
Signed-off-by: Ashley Cui <acui@redhat.com>
2025-04-04 01:48:19 -04:00
Ashley Cui
3b031a7745 GHA: Automate release
Automatically create release from tag, and build artifacts. Release notes are pulled from RELEASE_NOTES.

Signed-off-by: Ashley Cui <acui@redhat.com>
2025-03-28 10:54:56 -04:00
Paul Holzinger
af59e5c5be .github: remove cirrus rerun action
As pointed out in buildah[1] the action is broken in bad ways where it can
trigger 1000+ rerun wasting our cloud resources.

We have little flakes here and in general blindly re-rerunning is not a
the best so just get rid of it for now.

[1] https://github.com/containers/buildah/issues/6035

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
2025-03-07 17:29:29 +01:00
Chris Evich
bb4c73de5c [skip-ci] GHA/Cirrus-cron: Fix execution order
Fairly universally, the last Cirrus-Cron job is set to fire off at
22:22 UTC. However, the re-run of failed jobs GHA workflow was
scheduled for 22:05, meaning it will never re-run the last cirrus-cron
job should it fail.

Re-arrange the execution order so as to give plenty of time between the
last cirrus-cron job starting, the auto-re-run attempt, and the final
failure-check e-mail.

Signed-off-by: Chris Evich <cevich@redhat.com>
2022-12-06 10:37:09 -05:00
Chris Evich
effd4482e6 GHA: Add cirrus-cron rerun job
Also update the regular cirrus-cron checking job to reuse the podman
workflow instead of buildah.

Signed-off-by: Chris Evich <cevich@redhat.com>
2022-11-15 14:50:47 -05:00
Chris Evich
5a3c5d0b6c GHA: Add Cirrus-cron failure notifications
Requires: https://github.com/containers/buildah/pull/4088

This re-uses the buildah-workflow to send e-mail to podman-monitor if
any Cirrus-cron job failed, or the workflow itself fails.

Signed-off-by: Chris Evich <cevich@redhat.com>
2022-07-12 12:03:24 -04:00