On Wed, Jun 28, 2023 at 8:25 AM Ondřej Budai <obu...@redhat.com> wrote: > > > On Wed, Jun 28, 2023 at 2:20 PM Jonathan Steffan <jonathanstef...@gmail.com> > wrote: >> >> On Wed, Jun 28, 2023 at 5:23 AM Ondřej Budai <obu...@redhat.com> wrote: >>>>> >>>>> > Maybe I'm just using it wrong, but I've not found a different way. >>> >>> >>> I will take a look. The difference between livemedia and osbuildImage is >>> that the osbuildImage task is defined by a plugin and it interacts with >>> koji via the content generator API. Koji sometimes have issues presenting >>> information nicely for CGs. If anyone has more experience with Koji >>> internals, help would be definitely appreciated. >> >> >> It would be great to address this before adopting the proposed change. I do >> wonder if there is a way to change the "osbuildimage" to be much more >> similar to an "image" build. Or something like that. The information >> conveyed by an "image" vs "osbuildimage" is so much more useful. I don't >> know the Koji internals much anymore, but there has to be a way to make this >> better. >> >>> We can definitely flatten the JSON output into something that resembles a >>> log file. I will let you know when this is done. >>> >>> Note that every task also produces a manifest file - this is extremely >>> useful, because you can just feed it to osbuild locally. Since the manifest >>> basically fully specifies an image build (with locked package versions >>> including their hashes), there's a high chance that you will be just able >>> to reproduce the issue locally and use any tools you want for deeper >>> debugging. This is one of the goals of the project: Make image builds more >>> reproducible. >> >> >> Both the JSON and raw logs are useful. Very glad to know that the manifest >> will allow recreation of the build artifact. I'd like to see all of that >> presented similar to a build that packagers are used to (e.g. >> https://koji.fedoraproject.org/koji/buildinfo?buildID=2222698). Maybe this >> is more a Koji enhancement, but I still question moving this proposal >> forward without addressing the buildsys UX/UI. Let's be sure to not bury >> very useful things when making changes. > > > > Yep, that's a shortcoming of how we currently upload the builds to koji. It's > something we would like to tackle in the upcoming quarter, see the tracking > ticket: https://issues.redhat.com/browse/COMPOSER-1801 (public link). >
I can't comment on that ticket. :( -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ 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
