Setup lifecycle rules for the nightly updates s3 bucket

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
3 years ago
2 months ago

People

(Reporter: rail, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
... 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.
(Reporter)

Comment 1

3 years ago
Nick, do you think that 1m is enough here?
Flags: needinfo?(nthomas)
(Reporter)

Comment 2

3 years ago
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)
(Reporter)

Updated

3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
(Assignee)

Updated

2 months ago
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.