-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
False
-
None
-
False
-
Testable
-
-
https://pagure.io/centos-infra/issue/1399
Good morning!
So the Automotive SIG is building a fairly high number of kernels :] https://cbs.centos.org/koji/packageinfo?packageID=8886
Most of them go to -testing and end up on buildlogs: https://buildlogs.centos.org/9-stream/automotive/x86_64/packages-main/Packages/k/, fewer go to -release and end up on the final mirror: https://mirror.stream.centos.org/SIGs/9-stream/automotive/x86_64/packages-main/Packages/k/
We would like to reduce the number of packages on buildlogs: save space on the system + reduce the size of the metadata for the -testing repo.
IIRC, koji/cbs will garbage collect any build that isn't in a tag.
So if we remove these builds from the -testing tag to preserve buildlogs, how can ensure the builds aren't garbage collected? Should we leave them in -candidate? Should we have another tag -archived that we can move builds to?
Or is there a way to ask buildlogs to only pull something like the last 3 builds?
Thanks in advance for your guidance on this