Sep 12, 2025 10:44:04 AM Stephen Gallagher <sgallagh@xxxxxxxxxx>:
~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.
To my mind, we have three realistic options here:
For the record, they did the same thing for the rebuild a few weeks ago
last time the pyc magic number was bumped and it seemed to work well
enough. It was actually 3700 * 2 Bodhi updates (x2 for rawhide and f43).
Bodhi ended up catching up and each update got gated separately. The Go
SIG and I did something similar for the Go rebuild (400-500 updates for
each branch) the same weekend, and that procedure worked well enough for
us also. There were some signing infra failures (long-standing issue) and
CI infra issues (once Fedora CI team restarted Jenkins, everything caught
up without any extra intervention needed) that affected us, but those
were unrelated to either rebuild.
Doing one large side tag is untested and is unnecessary when there are no
build ordering issues (only Python needs to be updated and then
everything else can be built and submitted to Bodhi in any order). Also,
as Karolina said, one update that includes everything would block every
single build even if only one package fails gating. By doing an update
for each package, each gating failure can be handled independently by the
package's maintainer. Any solution that involves manually tagging builds
and skipping gating entirely is even less ideal and also creates more
work for releng.
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
