TMT: Initial Enablement

[lsm5]

No description provided.

[packit-as-a-service]

Failed to load packit config file:

Please correct data and retry.

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Please correct data and retry.

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Please correct data and retry.

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs[4].packages': 'Undefined package(s) referenced: containers-common-fedora.', 'jobs[5].packages': 'Undefined package(s) referenced: containers-common-centos.'})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs[4].packages': 'Undefined package(s) referenced: containers-common-fedora.', 'jobs[5].packages': 'Undefined package(s) referenced: containers-common-centos.'})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs[4].packages': 'Undefined package(s) referenced: containers-common-fedora.', 'jobs[5].packages': 'Undefined package(s) referenced: containers-common-centos.'})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[lsm5]

We can speed up tmt tests by only running the podman tests relevant to conmon. Let me know which ones and I can adjust the test config.

[lsm5]

@saschagrunert @haircommander With packit rpm build jobs in place, do we need the cirrus Packaging for Fedora N[-1] jobs? If no, I guess we could also delete contrib/ and .rpmbuild dirs along with those 2 jobs.

[lsm5]

Marking ready for review but maybe best to wait until containers/podman#24369 is merged. I'll then update the TMT plan to fetch tests from podman main branch instead of my own fork.

[saschagrunert]

@saschagrunert @haircommander With packit rpm build jobs in place, do we need the cirrus Packaging for Fedora N[-1] jobs? If no, I guess we could also delete contrib/ and .rpmbuild dirs along with those 2 jobs.

I'd say no, but I'm not exactly sure how we should handle the CI here.

[lsm5]

@saschagrunert @haircommander With packit rpm build jobs in place, do we need the cirrus Packaging for Fedora N[-1] jobs? If no, I guess we could also delete contrib/ and .rpmbuild dirs along with those 2 jobs.

I'd say no, but I'm not exactly sure how we should handle the CI here.

Doesn't look like any Cirrus job depends on fedora_packaging. So, I think it should be safe to remove. I can leave that for a followup though.

The current PR should be good to go. PTAL. I'll leave CentOS and aarch64 for a followup as well.

[lsm5]

Ah, there's still the fact that I'm fetching tests from my podman fork. I'll leave it to you if you feel comfy merging with that. I can keep my fork active and change the URL here once the podman PR is merged. Your call.

[lsm5]

@saschagrunert @haircommander How much does conmon care about nix package builds? Do we still need to keep the static build jobs?

[saschagrunert]

@saschagrunert @haircommander How much does conmon care about nix package builds? Do we still need to keep the static build jobs?

Yeah I would prefer keeping them because we still ship conmon this way.

[lsm5]

@saschagrunert @haircommander How much does conmon care about nix package builds? Do we still need to keep the static build jobs?

Yeah I would prefer keeping them because we still ship conmon this way.

ack, I'll get to those in another PR. Once the existing TMT tests pass here, I'll remove the Packaging for Fedora.. Cirrus jobs from here.