Extend Koji with a new feature that allows users to create installation media for various architectures.
Links to proposed work breakdown, design, etc - https://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/528
Requested for F26 to enable hub consolidation for s390.
Is this something more than the signed repos PR?
Look at the work outlined in the link above. I think Dennis Gilmore wanted to discuss the proposed design but there is more work than just signed repos.
This will need signed repos to be in
@mikem This is moving the making of the dvd iso and the install trees into koji as koji tasks
Metadata Update from @yulwang: - Issue priority set to: Low - Issue tagged with: groomed
@ausil Is this still valid? If yes, are there any clear requirements?
Metadata Update from @tkopecek: - Issue untagged with: groomed - Issue priority set to: None (was: Low)
Metadata Update from @tkopecek: - Issue tagged with: groomed
@jgreguske was the one that laid out the design, I just filed the ticket here, Jay would need to weigh in on if it is still desirable
It is still desirable to have Koji build installation media, but it is definitely not in my Q2 priorities (speaking internally about RH there). I've never understood the current model where only Pungi can build it. Koji is a much better place.
The implications of enabling Devs to build their own installation media is compelling to me. In the distant future we could do away with milestone composes, just take the latest that passed and ship that. Devs could be responsible for discovering dependencies are missing.
Metadata Update from @yulwang: - Issue priority set to: Normal
Metadata Update from @yulwang: - Issue tagged with: feature
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/koji/issues/157
Please continue any further discussion there.