mirror of
https://github.com/kata-containers/kata-containers.git
synced 2025-06-30 17:22:33 +00:00
ci: docker: Run the tests after the kata-static is created
There's no reason to wait till the payload is created to run the tests, as we rely on the tarball, not on the kata-deploy payload. That was a mistake on my side, and that's already fixed for the nerdctl tests. Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
This commit is contained in:
parent
12d833d07d
commit
c83f167c59
2
.github/workflows/ci.yaml
vendored
2
.github/workflows/ci.yaml
vendored
@ -74,7 +74,7 @@ jobs:
|
|||||||
file: tests/integration/kubernetes/runtimeclass_workloads/confidential/unencrypted/Dockerfile
|
file: tests/integration/kubernetes/runtimeclass_workloads/confidential/unencrypted/Dockerfile
|
||||||
|
|
||||||
run-docker-tests-on-garm:
|
run-docker-tests-on-garm:
|
||||||
needs: publish-kata-deploy-payload-amd64
|
needs: build-kata-static-tarball-amd64
|
||||||
uses: ./.github/workflows/run-docker-tests-on-garm.yaml
|
uses: ./.github/workflows/run-docker-tests-on-garm.yaml
|
||||||
with:
|
with:
|
||||||
tarball-suffix: -${{ inputs.tag }}
|
tarball-suffix: -${{ inputs.tag }}
|
||||||
|
Loading…
Reference in New Issue
Block a user