Re: Announcement: on-demand openQA testing of dist-git pull requests

Adam Williamson <[email protected]> Mon, 20 Jul 2026 22:58:44 +0100
Newsgroups gmane.linux.redhat.fedora.devel
Message-ID <[email protected]>
On Mon, 2026-07-20 at 22:53 +0200, Cristian Le via devel wrote:
> On 2026/07/14 8:19, Miroslav Suchý wrote:
> 
> > Dne 13. 07. 26 v 9:10 odp. Adam Williamson napsal(a):
> > > I don't want to invent some kind of system for marking PRs as related
> > > myself; we might want to do it as a project, though, and if we do go
> > > that way
> > 
> > Does it make sense to implement it as tmt-plan that can be triggered 
> > by Packit?
> > 
> > https://github.com/packit/tmt-plans
> > 
> > e.g. see this example https://github.com/packit/tmt-plans/pull/30/changes 
> 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. 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.
-- 
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