On Tue, 2023-06-27 at 17:59 -0600, Jonathan Steffan wrote: > > The Koji integration leaves many things to be desired. I've had to dig far > more than needed for osbuildimage stuff. > > For example, > https://koji.fedoraproject.org/koji/tasks?state=all&view=tree&method=osbuildImage&order=-id > is nearly useless to know what is going on. You have to go into each task > to find what you are looking for and you end up with some json logs > https://koji.fedoraproject.org/koji/taskinfo?taskID=102669680 and > ultimately finding a link to the build > https://koji.fedoraproject.org/koji/buildinfo?buildID=2222653 to get to the > image. Maybe I'm just using it wrong, but I've not found a different way. For compose debugging I don't think this part would be terrible in practice, most of the time. I agree that there not being any useful information about what each osbuild image each task is for, in the summary, is a pain. But *normally* how we wind up debugging failed composes is through the failed compose tracker: https://pagure.io/releng/failed-composes/issues which knows what each task is and tells you in the issue: https://pagure.io/releng/failed-composes/issue/5143 so you already know when you get to the task what it is, and the task logs usually are what we want to see. Personally I don't usually have much call for downloading the actual artifact from Koji - I'd usually get it from the compose - but maybe you have a workflow where it's important? Personally, I'm more worried about the logs being JSON. Machine- parseable is nice, I guess, but in practice it's usually humans who parse logs, at least in this case, and I see no really nice human way to consume that log. Opening it as raw JSON in my browser gives me a mess (it's not formatted for human consumption, and is stuffed with linebreak characters and stuff, much like ImageFactory logs). Opening it with a JSON-reading extension I have gives me a mess with more nested menus to click on. Opening it in a text editor gives me the same mess as opening it in the browser. Can we have this thing generate easily-human-readable logs as well as/instead of the JSON-formatted ones? -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@xxxxxxxxxxxxx https://www.happyassassin.net _______________________________________________ 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
