Hi Miroslav, Thank you for the clarification. I got a little bit lost reading the documentation and the source. So, after rereading, I understand that Fedora is not moving away from zuul to packit.dev, but from standard test interface to tmt: https://docs.fedoraproject.org/en-US/ci/#_enabling_tests

From your comments, I went ahead and followed an existing package, the "mock" project, hoping it is a good example.

So, for what I can understand, the .packit.yaml in the github repo defines how to build the tar ball and the srpms, which then it is built in copr triggered by packit.dev (I see a build per PR). I didn't find tmt tests here but my understanding is that they can be defined here and packit.dev would run them. This is the upstream if I understand correctly.

Then, somehow the update ends up in Fedora/CS dist-git (rpms/mock and rpms/mock-core-configs), the downstream. Them, zuul ci picks it up (since it is in rpms/* in the case of fedora) and runs the ci, which are ansible playbooks common to all, and one of them, rpm-tmt-test, runs found tmt tests in the rpms/_ repo itself. This involves builds on koji. If it passes, it is merged and built again in koji. Then, after that, I guess it goes the compose, more CI (like t_functional) and then pushing to mirrors.

I hope I didn't miss something.

The packit.dev reference in the cloud sig email is from the email "[CentOS-devel] CentOS Cloud SIG meeting minutes (2023-07-13)".

Thank you, Carlos.

On 7/25/23 04:55, Miroslav Vadkerti wrote:

Hi Carlos,

On Tue, Jul 25, 2023 at 12:15 PM Frantisek Lachman <flachman@redhat.com mailto:flachman@redhat.com> wrote:

---------- Forwarded message ---------
From: *Carlos Rodriguez-Fernandez* <carlosrodrifernandez@gmail.com
<mailto:carlosrodrifernandez@gmail.com>>
Date: Tue, Jul 25, 2023 at 4:53 AM
Subject: [CentOS-devel] [t_functional sig] Tests management with TMT
To: <centos-devel@centos.org <mailto:centos-devel@centos.org>>


Hi,

Is there any interest or already a plan to convert the test management
of the t_functional tests to TMT (https://github.com/teemtee/tmt
<https://github.com/teemtee/tmt>)?

Note that the conversion might not be even needed, tmt now serves well as a wrapper over various testing frameworks, many people use it like that.

I see that packit.dev <http://packit.dev> and tmt is where fedora is
trying to go instead of
zuul ci,

This might be a confusion, note that these systems are on different levels:

• Packit is on the level of upstream project GitHub / GitLab contributions

• Zuul CI for Fedora

https://fedora.softwarefactory-project.io/zuul/builds?job_name=rpm-tmt-test and Zuul CI for CentOS Stream https://centos.softwarefactory-project.io/zuul/t/centos/builds?job_name=rpm-tmt-test are on the level of dist-git contributions

All these run tmt tests which can be defined basically in any git repository (remote or local).

and also I saw the email from the cloud sig about adopting
packit.dev <http://packit.dev>. I was wondering how it will impact
t_functional.

Can you point me to that email please?

I have been playing with it and seems like a good tool for the job.

Glad to hear that :)

Best regards, /M

Regards,
Carlos.
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org <mailto:CentOS-devel@centos.org>
https://lists.centos.org/mailman/listinfo/centos-devel
<https://lists.centos.org/mailman/listinfo/centos-devel>

-- Miroslav Vadkerti :: Senior Principal QE :: Testing Farm / Linux QE IRC mvadkert #tft #tmt #osci :: Mobile +420 773 944 252 Remote Czech Republic :: Red Hat Czech s.r.o