action #111161
Updated by jlausuch about 2 years ago
Currently, we are testing images with podman and docker using different jobs: https://openqa.suse.de/tests/overview?distri=sle&version=15-SP3&build=_15-SP3_26.9_minimal&groupid=409 which sums up to ~40 jobs per image... At the beginning there was only base image, and not many updates. Today we have 20+ different images, so we could find a way to not spam openQA with so many jobs. Since we need to boot different Host versions to validate each container image, we can't group those jobs. However, we could group the jobs using the same qcow. e.g. `bci_on_SLES_15-SP3_host_podman` `bci_on_SLES_15-SP3_host_podma`n and `bci_on_SLES_15-SP3_host_docker` could be just `bci_on_SLES_15-SP3_host` and we run docker and podman tests in the same job. If we see that there are problems when using podman Also, `bci_on_AKS` and docker at `bci_on_EKS` shall be executed in the same time, we can also use snapshots in job, as they boot the jobs, but running docker and podman together should be supported. This way, we can tell which engines to run from the container-release-bot. For example, `init` and `pcp` images are not supported with docker and we are just running the jobs and skipping the test, it would be more efficient to not run docker tests at all. PC tools helper VM.