Learn more about these different git repos.
Other Git URLs
The actual dist-repo call/task allow to use --non-latest to ensure that other NVR are present in the generated repository. But it's actually just a boolean : only latest or all. It would be good to have a possibility to specify number of pkgs (like last 5 builds for example) so that once generated we don't keep/push out (to mirrors/CDN) if still tagged in some tags (I know untagging is the solution but in case of a community buildsystem, people wrote something to tag-build but rarely to untag)
dist-repo
--non-latest
Wouldn't GC rule fit more here? Something like:
tag <distro_tag> && order > 5 :: untag
Metadata Update from @tkopecek: - Custom field Size adjusted to None
You're right, I can (as a sysadmin not managing the tags) still enforce a rule (also based on regex to just target some tags like -release ones), and communicate that so that they know what to expect. And nothing to do at the dist-repo level. Thanks for the pointer :)
Metadata Update from @tkopecek: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
The above workaround works if you assume that all builds come from the same tag.
It would not be too much work for dist-repo to pass latest=N rather than a boolean, and this option is supported by the listTaggedRPMS call being used. However, the sorting that Koji will use for "latest N" might not be what is desired. The sorting there is the priority of tag inclusion from readTaggedBuilds, which is:
Metadata Update from @tkopecek: - Issue status updated to: Open (was: Closed)
Make sense, it should be relatively easy to add it. Scheduling for next release.
Metadata Update from @tkopecek: - Issue set to the milestone: 1.35
@tkopecek : just revisiting this ticket/request as we had Automotive SIG more or less asking for it They can still just untag-build themselves but from Infra/admin PoV that's easier to just announce a policy for the dist-repo task and implement it as users would often lack automation for "untag-build" operations, leading to growing usage
Metadata Update from @tkopecek: - Issue set to the milestone: 1.36 (was: 1.35)
I'm sorry, delaying this for next release as we don't have capacity to work on this now.
PR 4304
Metadata Update from @jcupova: - Issue tagged with: testing-ready
Metadata Update from @tkopecek: - Issue untagged with: testing-ready - Issue tagged with: testing-custom
Log in to comment on this ticket.