On Thu, Jan 16, 2020 at 02:09:45PM +0100, Aleksandra Fedorova wrote: > > While on one hand we don't need a long-term storage for development > builds, on the other: it is quite valuable to be able to compare the > latest successful build with some previous ones to see if we actually > improve anything over time. > > I am thinking on relying on ODCS composes to implement this part. > > If we setup ODCS pipeline and regularly build composes out of the > current content of the Koji tag, then we can store them elsewhere and > use as checkpoints: everything which has landed in such a compose can > be removed from Koji as soon as it is not used by the buildroot, i.e. > it is not the latest build for the component. > > Then we can implement a separate retention policy for composes which > may be more flexible. For example it may rely on whether or not this > compose was used in some advanced testing by anyone. Sounds reasonable. Thanks. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
