On Thu, 2025-07-31 at 15:42 +0200, Pavol Sloboda wrote:
> Hello,
> 
> I am currently reworking the tests for bodhi for Mariadb from STI to TMT as
> per the fedora change [0] and I came across an issue with the versioned vs
> unversioned rpms of Mariadb (this issue seems to be present in the STI
> tests as well), where the versioned mariadb rpms are named differently than
> the unversioned ones and I want to preferably keep the same tests for both
> kinds of packages by setting a flag for tmt or using the `-e` flag (or any
> other option) in `tmt run` to set an environment variable during
> the testing process in bodhi. Is there a way to do something like this? How
> exactly are the tests called inside of bodhi? I have gone over the
> documentation but I haven't found anything on this topic.

Just to correct one misconception - Bodhi doesn't do any test running
at all. Bodhi is only showing you test results, and doing some gating
based on them.

Bodhi gets the results from ResultsDB via greenwave. Any result that is
'for' the update itself or a package in the update will be shown.

The test in question likely runs in the ecosystem we somewhat vaguely
refer to as "Fedora CI" (we did an exercise once where we tried to
write down all the things that are part of Fedora CI, it was an eye-
opener). Cristian is part of the team handling that, so refer to his
response. I just wanted to clarify that Bodhi is not involved in
running tests at all.
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



-- 
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to