Bug 2342235 - Koji uses Red Hat Image Builder locally
Summary: Koji uses Red Hat Image Builder locally
Keywords:
Status: ON_QA
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Simon de Vlieger
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F43Changes
TreeView+ depends on / blocked
 
Reported: 2025-01-27 11:57 UTC by Aoife Moloney
Modified: 2025-08-09 18:45 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Aoife Moloney 2025-01-27 11:57:39 UTC
This is a tracking bug for Change: Koji uses Red Hat Image Builder locally
For more details, see: https://fedoraproject.org/wiki/Changes/KojiLocalImageBuilder

Switch the Red Hat Image Builder-built images in Koji to not build through a service, but locally.

If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.

Comment 1 Aoife Moloney 2025-01-27 12:01:47 UTC
Hi Simon, this is a gentle reminder that your change for F42 is required to be 'testable' by February 4th. This is our branching and changes testable milestone. Please refer to the docs page for the testable criteria and if you need to retarget to a later release at any stage, please do let me know and I will update the tracking bug and change page.

https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_change_process_milestones



Thanks!
Aoife

Comment 2 Simon de Vlieger 2025-02-03 18:40:27 UTC
@amoloney thank you. Could we target the beta freeze (18th of February)? There's some time needed to coordinate with infra :)

Comment 3 Zbigniew Jędrzejewski-Szmek 2025-02-25 18:06:37 UTC
That date has come and gone.

What is the status now? Can this still happen Beta next week?

Comment 4 Simon de Vlieger 2025-02-26 06:45:34 UTC
Hey @zbigniew.rozbicki, thanks for asking. This will hopefully happen after beta as koji was a bit more difficult than I anticipated, mostly regarding how we execute in buildroots and we're currently in freeze. We're also working on (some) infrastructure related bits which can be tracked here (https://pagure.io/releng/issue/12587). Since it doesn't affect the artifacts produced, only how they are produced I feel this should still be OK and the change doesn't need to retargeted to Fedora 43 but let me know what you think :)

Comment 5 Simon de Vlieger 2025-03-13 16:34:07 UTC
I'd like to re-target this change request to Fedora 43.

Initially I thought about doing this by adding a new plugin to the current `koji-osbuild` plugin. However, I've thought about that a bit more and I don't like it so I'll instead do this through a new plugin, which will need to go through package approval et al.

While it probably *is* possible to make this change before final it also isn't a particularly _good_ idea to rush reviews, deployments, and infrastructure config changes before final.

Comment 6 Simon de Vlieger 2025-08-07 19:27:58 UTC
All of the work for this change proposal has been implemented (see it's wiki page here, under scope: https://fedoraproject.org/wiki/Changes/KojiLocalImageBuilder). Fedora IoT has done its first nightly composes using the change and the last bit is the pending merge of: https://pagure.io/pungi-fedora/pull-request/1516 to also apply this to Fedora ARM Minimal.

Comment 7 Simon de Vlieger 2025-08-07 19:46:22 UTC
Sorry, status should be MODIFIED since 1 PR is open.

Comment 8 Simon de Vlieger 2025-08-09 18:45:17 UTC
Last PR has been merged as well, moving to ON_QA since this is now code complete and testable (well, already being tested) :)


Note You need to log in before you can comment on or make changes to this bug.