Currently chain-build is not usable without kojira (on the other hand, there are probably no deployments without it) as each stage waits via waitRepo on regeneration. Would it make sense to trigger newRepo before, so it is sure, that this moment will ever happen?
waitRepo
newRepo
It could spawn some unnecessary tasks, but given small race condition between finishing building stage and triggering newRepo vs. kojira's check, I think it is worth it.
And, chain-build also requires dest tag is inherited from build tag
dest tag
build tag
And, chain-build also requires dest tag is inherited from build tag Maybe some warning for this on CLI side?
or probably to check build_target in parent task?
build_target
I consider kojira to be required.
That said, I've been interested in overhauling how repo regens are triggered for a while. However, I don't think that simply calling newRepo from build tasks is the right way. We need to:
Metadata Update from @mikem: - Issue untagged with: easyfix
This is made obsolete by #4033 The waitrepo subtask that chain-build creates will request a repo, which indirectly triggers the regen.
Metadata Update from @mikem: - Custom field Size adjusted to None - Issue close_status updated to: Dropped - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/koji/issues/1129
Please continue any further discussion there.