Automatically getting rid of obsoleted builds

Miroslav Suchý msuchy at redhat.com
Wed Mar 19 16:27:41 UTC 2014


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?

-- 
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys


More information about the copr-devel mailing list