Closed Bug 1189889 Opened 11 years ago Closed 9 years ago

gecko-decision: Expire artifacts more aggressively (discussion)

Categories

(Taskcluster :: Services, defect)

Product:
Taskcluster
Component:
Services
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jonasfj, Unassigned)

Details

For try we should consider expiring artifacts faster than one year. We might want to keep logs for a long time. But large build artifacts could perhaps go away sooner.
Nick -- I heard that you might know what our data retention policy is for try and buildbot currently. If not, would you happen to know who the right person to ask would be?
Flags: needinfo?(nthomas)
On the ftp server we keep everything for 14 days, with no distinction between logs and binaries. bug 1193219 says treeherder has a 4 month retention. Historically this has been limited by space constraints, but I think devs are pretty much used to that timescale and copy files elsewhere if necessary (eg "please try out this <new feature>" blog posts).
Flags: needinfo?(nthomas)
Component: Integration → Platform and Services
didn't you fix this?
Flags: needinfo?(bstack)
Yep. Resolved in bug 1304180
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(bstack)
Resolution: --- → FIXED
Component: Platform and Services → Services
You need to log in before you can comment on or make changes to this bug.