Hey Kevin, On Mon, 2023-05-08 at 09:24 -0700, Kevin Fenzi wrote: > I'm broadly in favor here, some comments in line... > > ...snip... > > It will be beneficial to consider the > > [https://src.fedoraproject.org/container/fedora-toolbox > > fedora-toolbox] images as release-blocking deliverables because > > Fedora's [https://opencontainers.org/ OCI] infrastructure is often > > broken. Here are [https://pagure.io/releng/issue/11092 two] > > [https://pagure.io/releng/issue/11367 recent] examples of > > <code>fedpkg > > container-build</code> not working. In the second case, it was > > preventing the images from being rebuilt to pull in an > > [https://bugzilla.redhat.com/show_bug.cgi?id=2170878 important] > > bug-fix. The broken infrastructure prevents regular Fedora > > contributors from jumping in to rebuild and publish the images at > > critical points in the development schedule. Making them > > release-blocking deliverables would attract greater attention and > > scrutiny from release engineering and ensure that a Fedora > > development > > cycle does not proceed with broken or outdated or missing > > <code>fedora-toolbox</code> images. > > 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. > ;( Yes, I understand. Currently, what happens is that someone (very often Jens) jumps in to update the fedora-toolbox images from time to time, sometimes because users started to complain about missing images after branching or some other problem, then it turns out that Fedora's OCI infrastructure is broken, then it leads to a pagure.io/releng issue, and then someone (very often you, Kevin) jumps in to frantically debug and get things going again. I was hoping that by making the fedora-toolbox images release-blocking deliverables, we will avoid some of the ad-hoc frantic last-minute fire-fighting and get more eye balls on this part of the Fedora infrastructure. Most importantly, Fedora users would get a more robust and smoother user experience because they won't have to scream and yell on bug trackers to get new images pushed out the door. Also, it's not really possible to test the toolbox(1) binary unless the corresponding fedora-toolbox images are updated and published reliably. In practical terms, if this means that the Toolbx developers need to get involved to help out with Fedora's OCI infrastructure, then so be it. :) Cheers, Rishi _______________________________________________ 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
