On Fri, Sep 12, 2025 at 10:25:17AM -0700, Adam Williamson wrote: > On Fri, 2025-09-12 at 11:43 -0400, Stephen Gallagher wrote: > > ~3700 individual updates hitting Bodhi over a short period is almost > > certainly going to cause problems with the load, similar to trying to > > manually create a single update with all the same packages. > > I'm not really sure this is true. We get ~800 individual updates pretty > quickly with the ELN mass rebuilds, and that works fine, AFAIK. > > Bodhi is a reasonably sane webapp. Creating an update isn't an > *excessively* onerous operation in it. I can't really think why it > shouldn't be able to cope with creating 3700 relatively quickly. > > I can imagine it might cause signing to get backed up, but then, that's > a problem however we do this, isn't it? However you slice it, 3700 > packages need signing.
Well, if we do this in a named/releng created side tag we could also setup things to sign as builds complete. > It might back Fedora CI up a bit, I guess, since Fedora CI runs tests > on every new update. But a 3700-package megaupdate would cause more or > less the same load on Fedora CI I think (as it *mostly* tests at the > package level, not the update level). Only bypassing Bodhi entirely > would bypass Fedora CI. > > openQA should be fine as it only tests critpath stuff, and much fewer > than 3700 of the updates will be critpath. ok, if you think the load will be acceptable then we can give it a try that way. I still think a sidetag would be better (for the signing if nothing else), but either way... kevin -- _______________________________________________ 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
