https://src.fedoraproject.org/forks/pvalena/tests/ruby.git is your forked repository. Is this right?

Currently pointing to my fork(for testing), but will be later changed to tests/ruby (PR).

Sorry. You mentioned it.

Is there a document about ci.fmf that maybe is used by Fedora CI?

I know the following URLs.

• https://packit.dev/testing-farm/
• https://docs.fedoraproject.org/en-US/ci/

ci.fmf is a fixed name, right?

ci.fmf is a fixed name, right?

No, any .fmf format will do. It behaves the same way like on a localhost or on github CI. Please give it a go :).

Is there a document about ci.fmf that maybe is used by Fedora CI?

I know the following URLs.

• https://packit.dev/testing-farm/
• https://docs.fedoraproject.org/en-US/ci/

https://docs.fedoraproject.org/en-US/ci/quick-start-guide/
EDIT: sorry wrong link; that one's not updated yet.
Correct link: https://docs.fedoraproject.org/id/ci/tmt/

This is actually brand new (we had a talk & workshop recently on Nest with Fedora), but it should be enabled by end of this month. @mvadkert knows more.

No, any .fmf format will do. It behaves the same way like on a localhost or on github CI. Please give it a go :).

Sure. I am okay to give it a go. But if any file name is okay for <any name>.fmf, I wonder how you are setting the file name to be called. Fedora CI needs to recognize the ci.fmf is the config file to run the tests, right?

Any plan that is located will be executed (maybe just the first one, not sure - @mvadkert knows more). TMK what happens is: lookup (via tmt) for file with extension .fmf; it it has execute: section, it is considered a plan; and thus will be executed by CI.

@pvalena @jaruga Fedora CI recognizes all plans in the repository, does not need to be ci.fmf anymore. Also it will execute all plans found.

@mvadkert @pvalena thanks for the explanation. Now it's clear in my mind.