On Tue, 2023-05-02 at 14:20 -0700, Kevin Fenzi wrote: > On Tue, May 02, 2023 at 08:18:07AM +0530, Sumantro Mukherjee wrote: > > Hello > > > > > > This has been silent for a long time now but here's the update. > > Debarshi and I decided to re-write the whole thing as a changeset[0]. > > We DO care about not just the rpm but also the OCI image that we ship > > with Toolbx. As a result, we filed a releng ticket[1] where > > we justified the following: We need the image ready for branch point, > > beta and final and that image be blocked implying we resort to "no-go" > > if the expected image is not there at all. > > If we start building the oci image as part of composes, it will be not > failable, that is, if it doesn't compose, the compose fails and nothing > is produced. :) Of course, it might compose and still have some kind of > breakage and will need testing for that. > > Note that as far as I know there's not any critera/testing for branch > point. We just get a successfull compose there. Beta and Final are > actually releases with testing, etc. Right. I think just making it a non-failable image achieves everything desired. We can automate testing of the image, I guess, so long as there's an explanation somewhere of how we can test the specific image built as part of the compose when running the tests for e.g. the Workstation or Silverblue image from the same compose... -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@xxxxxxxxxxxxx https://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-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/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
