Re: Announcement: on-demand openQA testing of dist-git pull requests
Adam Williamson <[email protected]> Mon, 20 Jul 2026 23:29:28 +0100
| Newsgroups | gmane.linux.redhat.fedora.devel |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 2026-07-20 at 17:15 -0500, Cristian Le via devel wrote: > > On July 20, 2026 4:58:44 PM CDT, Adam Williamson <[email protected]> wrote: > > On Mon, 2026-07-20 at 22:53 +0200, Cristian Le via devel wrote: > > > In principle it could be added there, but: > > > - displaying the results could be very nasty > > > - it would be a bit wasteful to just wrap around another test suite > > > - making it on-demand or filtered to specific packages is something we > > > haven't solved yet > > > > > > As an alternative, I did consider if we could add it into > > > `packit-service` directly. The only blocker there I think is making it > > > trigger based on events (i.e. register a webhook on openQA to announce > > > when the state change) instead of having a process wait for the state to > > > change. > > > > Note: it seems openQA has webhook support - > > https://open.qa/docs/#setup-webhook-on-github - but this is the first > > I've heard of it, and I've never used it. > > It is also the opposite direction that we would need :). That is registering webhooks on github to trigger openqa, or in our case it would be registering a webhook on packit. > > What we have with packit-testing-farm is that packit registers the webhook onto testing-farm so that testing-farm reports when it finishes. If we replace testing-farm with openqa we would need a webhook on openqa. > > > Actual openQA scheduling in > > Fedora always runs through > > https://forge.fedoraproject.org/quality/fedora_openqa , which is built > > around fedora-messaging. Trying to bypass it and use openQA webhooks > > directly may not work properly as there's stuff the scheduler does > > (test variables it sets, specifically) which the tests rely on. > > And yeah the more I contemplate, the less of a bad idea it seems to me to just wrap it around a tmt test. It is not much different than the current implementation right? I still don't understand the idea here, honestly, or the problem it's trying to solve. Could someone explain it to me in small words? :D -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @[email protected] https://www.happyassassin.net -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new