After talking to Fedora QE, looks like it would be great if we could bring generic tests to stable Fedora release, where they could provide most of the value and even be a good candidate to get back gating of all components.
Acceptance criteria:
CC @bookwar @msrb @adamwill @kparal @psss
For the record, I'm going to look back at what happened last time we tried gating and see how many of the issues have been resolved by this point. Last time I think we tried to gate Rawhide; as discussed today, it's easier in many ways to start with gating stable releases, because there's less churn and we already by policy require interdependent packages to be bundled together in one update for stable releases, so it's less of a problem to fail an update because it's not together with another package it depends on.
Can we please have those tests available in Pull Requests? Figuring out a package does not even install in Bodhi update is quite good for packagers who choose not to use Pull Requests, but it is too late for those who do.
@adamwill The policy requires interdependent packages to be bundled together for all releases, even rawhide. https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages
+1 for enabling them also for pull requests! Now we have a possibility to run them via Testing Farm as it is integrated with Testing Farm. Can share more info on how to do it or our @guyinger can help out ...
@churchyard yeah, the policy requires it, but in practice I suspect it still rarely actually happens in Rawhide, outside of small package groups which have already opted in to some form of CI. I haven't done a systematic survey to check, though.
I'm in favor of this, but we need to fix https://pagure.io/fedora-ci/general/issue/155 first.
Log in to comment on this ticket.