Koji Cleanup

[Jay Greguske]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/05/2015 02:07 PM, John Florian wrote:
> What do you all do regarding cleanup of old koji tasks?  Do you
> just whack 'em with "find -mtime +N -delete" or is there something
> more appropriate?  I have 120G of livecd spins from my nightly
> builds and while I have lots of disk space I'm also suspecting that
> Koji is unconstrained until I do impose my own constraints.  True?
> 
> Also, perhaps related, can somebody explain to me how the --scratch
> affects spin-livecd jobs?
> 
> -- John Florian
> 

Without --scratch Koji will verify that every RPM that was installed
in the image is "known" by the Koji instance. That means either built
there, or as part of an external repository associated with a tag.
- --scratch images can include RPMs that were built locally or
downloaded randomly on the internet.

- --scratch builds are subject to a more aggressive garbage collection
policy and are put on a different part of the filesystem to
distinguish them. They live in /mnt/koji/scratch.

Without --scratch the provided kickstart file must be from a source
control manager too, it cannot be submitted from a local copy.

- - Jay


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)

iQEcBAEBAgAGBQJWPLzwAAoJEMzORChHoQ3aVqwIAIG9DVpX1mDk1lw3E+g3IlK0
KUM9T8O+CPlaZehs16GBtg9iXMqkFXozhC0GFL2/d+jVPyM3DAoDSRKY3vO5iVIQ
I4jSREkKszDdnk7xm5M1nA9Fn6EUfaLJewUJOyapPbxvtKMGswMUrmfoFe/Q2BOR
NRyK1lKj/gsrhY013wPN9fEiW+T2jc43oDAVQjx3C9bGBG12CujudcEeLwUtKn/2
F/gre9MBtpq4Bg0WOU2t6Way8NlbMiHneCEz+khZXqleRrLyKyFsL5tqX6dMYSzJ
ofxA31lj/d8KLPOGzuVDU3K3r0RrY697DrDw/bB6Uk/t4rr8sRFAoQV4FpwoxFw=
=Q39b
-----END PGP SIGNATURE-----