People just need a way how to do scratch builds of modules. It means the module builds which would be garbage collected after few days. My ideas how to do that:
module-build
"scratch": True
builds
views.py
ModuleBuild.json()
scratch
reuse_component
utils.py
scratch=True
scratch_module=True
scratch-builds
KojiContentGenerator.py
pdc-updater
active=True
unreleasedvariants
producer.py
build.koji_tag
build.koji_tag + "-build"
Since this is touching multiple projects, if we decide this is a way how to implement this, we should create separate tickets for other projects like rpkg, pdc-updater and pdc.
Hm, yes. We are +1 to this.
@mikeb thinks that we should call the value something other than scratch, just because that is a loaded term and people may end up confused by it (since the rpm builds will still be real builds).
How about --temporary for the rpkg argument and calling them temporary or module_temporary everywhere?
--temporary
temporary
module_temporary
A big +1 as a user. I will be much less likely to start using modules seriously if I can't do scratch build locally and on the build servers.
FWIW, you can do local builds today. The big missing piece here are scratch builds in the mbs/koji servers.
QE is missing this scratch build feature.
@merlinm is in the process of writing this feature in #1136.
This was implemented by #1136, which has been merged and released. It was deployed to the Fedora MBS infrastructure this week.
Metadata Update from @merlinm: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.