From ec290853e9939a3b5ac4f87d0746aaa91270ef8d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Mon, 10 Feb 2025 18:03:25 +0100 Subject: [PATCH] workflows: build: Do not store unnecessary content on the tarball MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Otherwise we may end up simply unpacking kata-containers specific binaries into the same location that system ones are needed, leading to a broken system (most likely what happened with the metrics CI, and also what's happening with the GHA runners). Signed-off-by: Fabiano Fidêncio --- .../build-kata-static-tarball-amd64.yaml | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/.github/workflows/build-kata-static-tarball-amd64.yaml b/.github/workflows/build-kata-static-tarball-amd64.yaml index dc3520f146..e1d7ec2a29 100644 --- a/.github/workflows/build-kata-static-tarball-amd64.yaml +++ b/.github/workflows/build-kata-static-tarball-amd64.yaml @@ -218,9 +218,24 @@ jobs: strategy: matrix: asset: - - agent + - busybox - coco-guest-components + - kernel-nvidia-gpu-headers + - kernel-nvidia-gpu-confidential-headers - pause-image + steps: + - uses: geekyeggo/delete-artifact@v5 + with: + name: kata-artifacts-amd64-${{ matrix.asset}}${{ inputs.tarball-suffix }} + + # We don't need the binaries installed in the rootfs as part of the release tarball, so can delete them now we've built the rootfs + remove-rootfs-binary-artifacts-for-release: + runs-on: ubuntu-22.04 + needs: build-asset-rootfs + strategy: + matrix: + asset: + - agent steps: - uses: geekyeggo/delete-artifact@v5 if: ${{ inputs.stage == 'release' }} @@ -229,7 +244,7 @@ jobs: build-asset-shim-v2: runs-on: ubuntu-22.04 - needs: [build-asset, build-asset-rootfs, remove-rootfs-binary-artifacts] + needs: [build-asset, build-asset-rootfs, remove-rootfs-binary-artifacts, remove-rootfs-binary-artifacts-for-release] steps: - name: Login to Kata Containers quay.io if: ${{ inputs.push-to-registry == 'yes' }}