Closed Bug 1193505 Opened 10 years ago Closed 10 years ago

only keep release build dirs for 10 days

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(firefox43 fixed)

RESOLVED FIXED
Tracking Status
firefox43 --- fixed

People

(Reporter: bhearsum, Assigned: bhearsum)

Details

Attachments

(3 files)

We hit a lot of out of space issues on Windows in 40.0. Nick theorized that this was in part due to increasing the number of l10n chunks - meaning there's a lot more directories that can't be cleaned up for 45 days. We realized that we never go back and look at these directories after so long. Keeping them around for a week was suggested, because occaisonly we find issues during the build process that are easy to recover from with a builddir. Let's round that up to 10 days to be safe.
Most of this is in tree now. I'm tempted not to bother backporting to aurora and higher, since mozilla-central/inbound/try jobs will most likely run on every slave within 10 days anyways...
Assignee: nobody → bhearsum
Status: NEW → ASSIGNED
Attachment #8648157 - Flags: review?(nthomas)
Attachment #8648155 - Flags: review?(nthomas) → review+
Comment on attachment 8648157 [details] [diff] [review] lower purge time in mozharness configs runner too ?
Attachment #8648157 - Flags: review?(nthomas) → review+
Attachment #8648155 - Flags: checked-in+
Whiteboard: [leave-open]
This is pretty much the same as the other two patches so I just went ahead and landed it.
Attachment #8649259 - Flags: checked-in+
Whiteboard: [leave-open]
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
In production
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: