From e8e916be9d84827cb939c56b544fc0fa8129464d Mon Sep 17 00:00:00 2001 From: Colin Walters Date: Wed, 23 Sep 2026 06:50:27 -0400 Subject: [PATCH] ci: Keep package artifacts for a week instead of a day The integration test jobs consume the RPMs built by the package job in the same workflow run. With a 1 day retention, re-running a flaked test job on a PR that has been sitting for more than a day fails with "Artifact not found for name: packages-", and the only way out is re-running the whole workflow, including rebuilding the packages. The tradeoff is storage: each packages- artifact is about 8MB, and at recent volume (~10-25 runs a day, 5-6 OSes) a week of them is a few GB at steady state rather than a few hundred MB. That's still small next to the tmt-log artifacts each run uploads with the default 90 day retention (tens of MB each, dozens per run), and artifact storage isn't billed for public repositories anyway. We could go longer if a week turns out not to be enough. Related: https://github.com/bootc-dev/bootc/issues/2177 Generated-by: AI Signed-off-by: Colin Walters --- .github/workflows/ci.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 51490f76ef..94601538e2 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -278,7 +278,9 @@ jobs: with: name: packages-${{ matrix.test_os }} path: target/packages/*.rpm - retention-days: 1 + # Test jobs download these from this run; keep them long enough + # that re-running a flaked job on an older PR still works. + retention-days: 7 # Unit tests don't depend on the variant/filesystem/bootloader/boot_type/seal_state # axes used by the test-integration matrix below, so we run them once per OS here