Article proposal: Introducing Log Detective for Packit builds

Article Summary: Introduce new Log Detective integration with Packit and describe how it will work.

Article Description:
Article will present audience with new integration of Log Detective and Packit,
explaining basics of Log Detective service and how communication between Log Detective and Packit will be conducted.

Since both Log Detective[1] and Packit have been deployed in production for some time now, focus won’t be on either of the services, but on what functionality will Log Detective provide for Packit and how will it be delivered.

Final section of the article will make note of upcoming extension of Log Detective analysis to Packit builds executed in COPR.

[1] Log Detective can now explain build log failures

I have read and understand the Ai-Assisted Contributions Policy

This is probably better suited for the Fedora Community Blog, but I’m not against publishing it on Fedora Magazine.

commops-team Do you have an opinion about this?

@jpodivin If you want to pursue this article, please use comments on this topic if you have questions or need to communicate with the editors about anything.

The overall work flow is described at this link as well as other helpful information.

This site might contain some items of interest

The articles are written using the WordPress instance for the Fedora Magazine.
From the menu in the left column of that page, select
*Posts>Add New Posts
to open the new article to edit and get started.

When you have it ready to review in the Fedora Magazine WordPress site, please leave a comment in this topic, with a preview link, and we will start the review process.

Thanks for volunteering to write for the Fedora Magazine!

I don’t have particular preference regarding the venue. If it is a consensus that this article should go into community blog, rather than the magazine, I would gladly publish it there.

@jpodivin to me the venue for this article depends on who is likely to benefit from it. If the use of Log Detective and Packit are likely to be of general use in the greater Fedora community then the magazine is fine. If the implementation and your description is primarily for the integration in the Fedora project developers environment then the Community blog is perhaps more reasonable.

Since I am not in the development environment I can only say that I suspect the Community Blog might be better.

Ultimately your choice, however.

I was hoping to get someone from the commops-team, who run the the Fedora Community Blog, to opine. Maybe @jflory7? But I think Justin might be on PTO.

The packit is available to all people who wish to package a project for Fedora. But yes, it is really just for developers. Can I try publishing it in the magazine, and if it’s rejected there, try the community blog?

I was trying to give the Community Blog a chance to take this one since I think it might be of more interest to the packagers and development community than it would be to the Fedora Linux end-users. But they don’t seem to be paying attention, so let’s go ahead and run this on Fedora Magazine. At least we can say we gave them a chance to score the content. :slightly_smiling_face:

@jpodivin: Go ahead and upload your article here: Magazine - Dashboard

Then let us know with a follow-up comment here when you think it is ready for review and publication on Fedora Magazine.

Thanks for contributing to Fedora Magazine! :slightly_smiling_face:

@glb Thank you very much. I’m going to update the article and put it there.

@glb Sorry it took so long. I’ve just submitted the article for review.

LGTM. :slightly_smiling_face:

@rlengland do you want to schedule this?


There might be one small problem with the cover image. It looks like the text might be a little too close to the left/right margins. Also, it’s just my opinion, but I would make the text a little bolder.

The text is right on the edge of the boundary but it DOES fit. I’ll schedule this for tomorrow 13 May

@rlengland Hi. I hate to bother you about this. Could we clarify that Log Detective is handling scratch builds?

Would be also nice to mention we are talking about dist-git PRs…

So, instead of:

Starting this month, Log Detective will provide an analysis of failed Koji builds in the Packit service.

Use something along the lines:

Starting this month, Log Detective will provide an analysis of failed Packit-triggered scratch Koji builds on dist-git pull-requests.

@jpodivin @lachmanfrantisek I have replace the sentence with the one suggested.