On Mon, May 08, 2023 at 07:57:30PM +0000, Zbigniew Jędrzejewski-Szmek wrote: > > I think we need some clarity wrt. to the dependency order here. > Let's say we: > > In order to do this at branch point, we will need to move building this > > image into the compose process and mark it blocking. > OK, so we build things, but then we need to publish to registry.fp.o, > which is asynchrounous (?). When we test the newly built ISOs, do No, it happens at the end of the compose (if no blocking deliverables failed causing the compose to fail) > we test them also with the latest image that we get from registry.fp.o? > And if we find a bug anywhere in this pipeline, we respin everything? Good question. I'll note that currently we do not do any specific testing after branch point. We freeze things to get a compose to complete, but then we move on. It's not like Beta or Final. > > I'd like to note that making this blocking doesn't waive any kind of > > magic wand that makes our infrastructure more reliable. ;) > > The container build pipeline is a long collection of fragile things. > > It may well result in us slipping more based on things not working. ;( > > Hmm, quoting from https://pagure.io/releng/issue/11092: > >> Also the aarch64 cluster is running on Fedora 33 boxes, so we > >> should probably try to do a full redeploy :-( > > We can't upgrade it from f33 because docker is no longer in f34+ and > > openshift origin / 3.11 doesn't support any newer either. > > Is this still true? I don't think we want to make the Fedora release > process contingent on something that requires F33. yes, it's still true. Note thats the aarch64 osbs cluster. The x86_64 one is rhel7. So, perhaps it would make sense to only make the x86_64 one blocking? kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
