I'm not sure exactly what is comprised on buildhost, but I can say that the public tree is loaded with out of date images. It might make sense to simply delete any images older than, say, a month.
On Mon, May 12, 2008 at 6:09 AM, Graeme Gregory <[EMAIL PROTECTED]> wrote: > Hi, time to bother you again. > > But our admin team have pointed out that we are filling the disk on > buildhost very fast. But something we seem to lack for buildhost are > any policies on how it should be used. I am loath to demand a bigger > machine from admin guys until we have it decided how we actually want > to use buildhost going into the future. > > So my opinions. > > 1) Buildhost is for building our official feeds and images. > 2) Buildhost is not a debugging environment. > 3) Due to 2) rm_work can be used. > 4) We shouldnt expose the build tree as is public, it just causes > confusion like the .summary one. > 5) Most builds should be incremental with maybe once a week/month a > clean of tmp/ is done. With Holgers changes to PERSISTANT_CACHE we > no longer lose git SRCREV increments. > > But these are just my opinions. Hence why I send an RFC so distro team > can choose best policies going forward. > > Graeme > > >
