On Tue, 2021-06-22 at 18:46 -0400, Neal Gompa wrote: > On Tue, Jun 22, 2021 at 6:42 PM Florian Weimer <fwei...@redhat.com> wrote: > > > > * Matthew Miller: > > > > > On Sun, Jun 20, 2021 at 09:48:15AM -0700, Adam Williamson wrote: > > > > We've talked about various concerns around this in the past (the > > > > technicalities of exactly how to implement it, and the concern that not > > > > enough composes actually meet the requirements so we'd wind up with few > > > > composes synced and a big disconnect between what's in the repos and > > > > what's in Koji), but the *idea* has been there all along and I agree > > > > with Neal that it was tied up with 'no more Alphas'. > > > > > > What happened with Dennis Gilmore's idea of making two levels of "rawhide" > > > rawhide, one like it is today (but not pushed to mirrors), in addition to > > > a > > > fully gated one? > > > > The ungated rawhide (aka the buildroot) is not pushed to mirrors today. > > The discrepancy between buildroots and mirrors is a significant source > > of developer confusion, I think. > > > > No. This never got implemented. There is Rawhide gating and such, but > we've never blocked syncs out to the master mirror. > > And for having two levels of rawhide, we'd need both levels synced to > the mirrors to be useful. Otherwise people can't really effectively > use it.
I think you're talking about different things. Matthew was referring to a plan (AIUI) to have two locations where "Rawhide" composes would be synced, one where all completed composes would be synced (as today), one where only composes that passed gating would be synced. I don't recall this plan, and don't know what happened to it, but that's what the idea was, I think. Florian seems to be talking about how Rawhide builds go into the buildroot as soon as they pass Bodhi and get tagged, so other package builds start pulling them in right away, but those builds may not make it out to the public repos (which testers and packagers consume) for some time if composes are failing. That's a rather different thing and doesn't really have anything much to do with "gating" per se, but it is worth noting that this would likely only become a more significant issue if we started gating Rawhide compose sync on *tests passing* as well as the compose completing. The more stuff has to work before we sync a compose, the bigger the gap between what's in the buildroot and what's in the repos can grow, potentially. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha 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 on the list, report it: https://pagure.io/fedora-infrastructure
