On 15-07-2024 10:24, Pavel Raiskup wrote:
TL;DR: We plan to start monitoring build activity in Copr projects. If no builds appear for a long time in these "rolling" chroots (such as Fedora Rawhide), we'll disable such chroots, preserve the built results for a while, and then delete them if no action is taken by the user.
Thanks for the very early heads up. Will you provide more details regarding build retention? Without it it's kinda hard to judge the impact.
I can think of at least one project I'm looking after that won't see many updates. It's kind of there for convenience.
I'm regularly using the _delete after_ option as well as _max number of builds_ for packages being automatically rebuilt. I'd like to see a project wide option allowing me to specify max builds to keep regardless of age or an option to rebuild for rawhide when its associated release is incremented. The latter sounds more difficult to implement and may have unintended side effects if not thought through.
-- Sandro -- _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
