Closed Bug 556479 Opened 16 years ago Closed 16 years ago

Try server build list needs culling/expiry

Categories

(Mozilla Messaging Graveyard :: Release Engineering, defect)

Product:
Mozilla Messaging Graveyard
Component:
Release Engineering
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: standard8, Assigned: gozer)

References

(
URL
)

Details

http://s3.mozillamessaging.com/build/try-server/list.html seems to have stopped being added to since 22 March. Its probably time we cleaned up a few builds on there anyway, but if we want to do that, we should propose a clean up schedule first anyway (e.g. 1 year or something).
Looks like it's a side effect of having hit more that 1000 files in there. By default, the amazon S3 list API only returns up to 1000 items. The only way to get more data out would require changing list.html to use an existing old file as starting point. Definitely a better solution to setup the cleanup sechedule and watch for 1000 files in there. the oldest file currently in there is from 2009-03-27, so already older than a year. I'd probably suggest something a bit more conservative, like 6 months. Thoughts ?
If we still a try build after 6 months there are serious flaws in either the patch/bug/feature, or in our process. 6 month seems very reasonable to me.
If we settle on a default policy of 6 months, I can automate cleaning it up, and exceptions can be made. 6 months, going once ?
Summary: Try server build list has stopped updating → Try server build list needs culling/expiry
6 months twice !
I'm going drop a note to tb-planning. Give it 24 hours.
No responses, do it!
Done.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.