run clobbers after release

RESOLVED FIXED

Status

P3
normal
RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: catlee, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
even though we always clobber the current release that's underway, there's nothing in place to ensure that old releases get clobbered eventually.

maybe we should clobber previous releases after some amount of time has passed (a few weeks?)

This is particularly painful for infrequent ESR releases. Unless we clobber these, they will eat up disk space for 6 weeks on the slaves they ran on.
Priority: -- → P3
Product: mozilla.org → Release Engineering

Comment 1

5 years ago
IIRC we clobber release build directories after 45 days. Is this correct?
Flags: needinfo?(jhopkins)
Yes, purge_builds.py[1] now accepts an expiry age on ignored directories.  The expiry value is defined in buildbotcustom[2].

[1] http://hg.mozilla.org/build/tools/file/07018a1da0d8/buildfarm/maintenance/purge_builds.py#l136
[2] http://hg.mozilla.org/build/buildbotcustom/file/91915daf0b93/process/factory.py#l384
Flags: needinfo?(jhopkins)

Comment 3

5 years ago
\o/
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.