koji

#2179 RFE: koji merge-sidetag command
Opened by ignatenkobrain. Modified

Open
Close Issue

We have our own deployment of koji in our company and we started finally to use side tags, however I found out that there is no easy way how to merge side tag back "properly". What I would like it to do is:

  • Figure out proper tag automatically (not sure if this is possible to find mapping between build tag → destination, but probably if build tag is used only for one target, it could use that, otherwise ask for target)
  • Check if there are any newer builds in destination target and reject merge before doing any tagging
  • Tag all builds at once (atomically), if any tagging fails, revert back

Not sure how hard would it be to implement, but would save us a lot of time and nerves :)

@tkopecek

Related #1384

Metadata Update from @tkopecek:
- Custom field Size adjusted to None

Metadata Update from @tkopecek:
- Issue set to the milestone: 1.22
  • Who should be able to do that? I expect, that there would be no special rules. If policy allow such tagging, it can be done
  • What means "newer builds" - later tagged or higher NVR? (I would prefer later tagged which is more in line with how the koji works)
  • Atomic tagging is not possible - API is doing it one by one. So if it will fail, we can untag them which can result in a problem also (but less frequent as policy was already tested during tagging)

Who should be able to do that? I expect, that there would be no special rules. If policy allow such tagging, it can be done

yes, I imagine it this way. If you can't tag at least one of the RPMs, the whole merge should be reverted.

What means "newer builds" - later tagged or higher NVR? (I would prefer later tagged which is more in line with how the koji works)

I think making it consistent with koji - latest tagged (is not it latest built?)

Atomic tagging is not possible - API is doing it one by one. So if it will fail, we can untag them which can result in a problem also (but less frequent as policy was already tested during tagging)

Probably it is time to do the tagBuild for multiple packages? I think tagBuildBypass does something similar, so probably this is just about wrapping it somehow.

Metadata Update from @tkopecek:
- Issue set to the milestone: 1.23 (was: 1.22)

Metadata Update from @tkopecek:
- Issue set to the milestone: None (was: 1.23)

@tkopecek any news here?

I've not time to do this one yet :-( I've removed it from planning for now. I can't promise that it will be in near future if there is no one else picking it.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/2179

Please continue any further discussion there.
Metadata
None
None
None
None
Low
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.