release: Don't ship the pause-image

It doesn't make sense to ship the pause-image itself as an release
artefact.

The reason we build it and cache it is in order to use it inside the
rootfs, and that's it, there's not need to ship it as part of the
release, at all.

Fixes: #9032 -- part II

Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
This commit is contained in:
Fabiano Fidêncio 2024-02-13 09:45:50 +01:00
parent 00be9ae872
commit 0462b33a5b
No known key found for this signature in database
GPG Key ID: EE926C2BDACC177B
2 changed files with 5 additions and 0 deletions

View File

@ -68,6 +68,8 @@ jobs:
stage: release
- asset: cloud-hypervisor-glibc
stage: release
- asset: pause-image
stage: release
steps:
- name: Login to Kata Containers quay.io
if: ${{ inputs.push-to-registry == 'yes' }}

View File

@ -38,6 +38,9 @@ jobs:
- virtiofsd
stage:
- ${{ inputs.stage }}
exclude:
- asset: pause-image
stage: release
steps:
- name: Take a pre-action for self-hosted runner
run: ${HOME}/script/pre_action.sh ubuntu-2204