In my rhughes/f20-gnome-3-12 COPR I build the entire GNOME stack and the few deps it needs automatically. What I didn't know is that old successful builds still remain in the repo, which leads to things like this:
Available gtk3-3.11.6-1.fc20.src (rhughes-f20-gnome-3-12) Available gtk3-3.11.7-1.fc20.src (rhughes-f20-gnome-3-12) Available gtk3-3.11.8-1.fc20.src (rhughes-f20-gnome-3-12) Available gtk3-3.11.9-1.fc20.src (rhughes-f20-gnome-3-12) Available gtk3-3.11.9-2.fc20.src (rhughes-f20-gnome-3-12)
Is there a way of automatically (or using some API) deleting the old builds? I *really* don't want to wade through 41 pages in the "Builds" tab, nor do I want to click [delete] ~300 times...
Ideas welcome. Thanks.
Richard.
On 03/19/2014 04:22 PM, Richard Hughes wrote:
In my rhughes/f20-gnome-3-12 COPR I build the entire GNOME stack and the few deps it needs automatically. What I didn't know is that old successful builds still remain in the repo, which leads to things like this:
Available gtk3-3.11.6-1.fc20.src (rhughes-f20-gnome-3-12) Available gtk3-3.11.7-1.fc20.src (rhughes-f20-gnome-3-12) Available gtk3-3.11.8-1.fc20.src (rhughes-f20-gnome-3-12) Available gtk3-3.11.9-1.fc20.src (rhughes-f20-gnome-3-12) Available gtk3-3.11.9-2.fc20.src (rhughes-f20-gnome-3-12)
Is there a way of automatically (or using some API) deleting the old builds? I*really* don't want to wade through 41 pages in the "Builds" tab, nor do I want to click [delete] ~300 times...
Ideas welcome. Thanks.
Old successful builds are kept for 14 days. Then they are removed. But just the from yum repository. Entries in DB (and in Builds tab) are kept forever.
The code for removal of old builds is here: https://git.fedorahosted.org/cgit/copr.git/tree/backend/copr-prune-repo
Is it enough for you? Or you have some reason to remove successful builds earlier?
On 19 March 2014 16:27, Miroslav Suchý msuchy@redhat.com wrote:
Old successful builds are kept for 14 days. Then they are removed. Is it enough for you?
Ahh, so I probably don't need to worry. I had visions on having 25 versions of every package in the metadata.
Thanks,
Richard.
On 03/19/2014 05:38 PM, Richard Hughes wrote:
Ahh, so I probably don't need to worry. I had visions on having 25 versions of every package in the metadata.
Yes. No worries. :)
The reason why I kept old builds for some time, is that you can e.g build 5 new versions of the same package during one hour. But some random user have yum metadata 4 hours old. And if Copr would keep only newest package and user will call "yum install" he will get 404 and will be forced to "yum clean metadata". With keeping old builds for some time, this will not happen. And as bonus, during that 14 days period, user can even call "yum undo" to revert installation if he found it broken.
copr-devel@lists.stg.fedorahosted.org