containers
CI: is cirrus still needed here?
There seems to be three different CI providers in use cirrus, github actions and packit/tmt.
Can we drop cirrus here to simplify our on management, looks like none is taking care to update the VM image son this repo https://github.com/containers/conmon/pull/528
There are only a few tasks so I guess they can be migrated to run with tmt ot github action, https://github.com/containers/conmon/blob/main/.cirrus.yml?
I don't think GH gives us the best for running the cri-o tests but i am open to moving away from it.
Looks like @lsm5 is already working one some tmt tests here https://github.com/containers/conmon/pull/538
I think that is likely the best option for this repo as we can reuse podman upstream tests that run here than without much (if any duplication) and then for cri-o one could do the same.
There a bunch of static nix build tasks here, are the binaries that they build actually used anywhere or could they be dropped? But even if they are still needed I guess the nix builds can be migrated to any CI tooling really.
It seems the best would be to convert cirrus to Github actions for now as TMT tests are still work in progress?
github actions runs as container with a more limited access compared to the full VMs of cirrus or tmt. If you try to run containers here as part of the tests that might matter.
Anyway my goal is not to create busywork, if the current setup works for you then by all means we can keep using cirrus. I was just evaluating because the image ID updates were not being done actively here but it seems you updated to a recent version in https://github.com/containers/conmon/commit/3b997548f725573f24336e1bff7785902065f891 so that should be good now as well.