Closed Bug 1176554 Opened 9 years ago Closed 9 years ago

Setup lifecycle rules for the nightly updates s3 bucket

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rail, Unassigned)

References

Details

... mostly for archaeological and debugging purposes. Generated partial are usually bitrot in 24 hours because of a new nightly generated every day. Merge day freeze on aurora is an exception.

We can start with a rule to delete files older than 1 month.
Nick, do you think that 1m is enough here?
Flags: needinfo?(nthomas)
We can also archive the files to Glacier if needed.
1 month would match what we have for desktop apps on ftp.m.o right now. It probably wouldn't matter if we went shorter for nightly updates, a couple of weeks or something. For Aurora we'll need to handle the freeze anyhoo, ie a partial from the freeze point to the builds after we unfreeze.

Very occasionally we want to look at older mar files, but I'm not sure it's worth having them on Glacier. The LIST operations will start returning a lot of data.
Flags: needinfo?(nthomas)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.