summaryrefslogtreecommitdiff
path: root/.cirrus.yml
diff options
context:
space:
mode:
authorEd Santiago <santiago@redhat.com>2022-07-12 08:28:21 -0600
committerMatthew Heon <matthew.heon@pm.me>2022-07-26 13:04:19 -0400
commitca4630ede6d50e3417502a7d31ef60576f371b8c (patch)
tree3d15a3fad104473977ac31eb537499e312a9484c /.cirrus.yml
parentbf269e634caee2022e99189de8337bd7fcd8f0e7 (diff)
downloadpodman-ca4630ede6d50e3417502a7d31ef60576f371b8c.tar.gz
podman-ca4630ede6d50e3417502a7d31ef60576f371b8c.tar.bz2
podman-ca4630ede6d50e3417502a7d31ef60576f371b8c.zip
CI: sanity check for desired runtime
We're still not testing runc in CI (#14833), and it may be weeks or months before we can, due to criu/glibc nightmare, but one day we'll be back on track, then later on we'll update VMs again, and screw it up, and lose runc, and not notice, and RHEL will break, and oh noes headless chicken again, repeat repeat. We can do better. Use .cirrus.yml to explicitly define which VMs should use which runtimes, and enforce it early in the CI build step. This should never fail (uh huh) in a PR, only in one of the update-VM PRs. Signed-off-by: Ed Santiago <santiago@redhat.com>
Diffstat (limited to '.cirrus.yml')
-rw-r--r--.cirrus.yml4
1 files changed, 4 insertions, 0 deletions
diff --git a/.cirrus.yml b/.cirrus.yml
index 81bbe7c8f..14d3540c1 100644
--- a/.cirrus.yml
+++ b/.cirrus.yml
@@ -167,14 +167,18 @@ build_task:
VM_IMAGE_NAME: ${FEDORA_CACHE_IMAGE_NAME}
CTR_FQIN: ${FEDORA_CONTAINER_FQIN}
# ID for re-use of build output
+ CI_DESIRED_RUNTIME: crun
- env: &priorfedora_envvars
DISTRO_NV: ${PRIOR_FEDORA_NAME}
VM_IMAGE_NAME: ${PRIOR_FEDORA_CACHE_IMAGE_NAME}
CTR_FQIN: ${PRIOR_FEDORA_CONTAINER_FQIN}
+ CI_DESIRED_RUNTIME: crun
- env: &ubuntu_envvars
DISTRO_NV: ${UBUNTU_NAME}
VM_IMAGE_NAME: ${UBUNTU_CACHE_IMAGE_NAME}
CTR_FQIN: ${UBUNTU_CONTAINER_FQIN}
+ # FIXME 2022-07-12: change to runc once #14833 is fixed!
+ CI_DESIRED_RUNTIME: crun
env:
TEST_FLAVOR: build
clone_script: *full_clone