Closed
Bug 384949
Opened 17 years ago
Closed 17 years ago
Some nightly directories are not transferred to archive.m.o
Categories
(mozilla.org :: FTP: Staging, task, P3)
mozilla.org
FTP: Staging
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: nthomas, Assigned: nthomas)
Details
The script which moves dated directories from ftp.m.o to archive.m.o curretly processes these directories: mozilla/nightly firefox/nightly thunderbird/nightly seamonkey/nightly xulrunner/nightly It's an important part of keeping disk usage under control on ftp.m.o and its staging server. The first dir is now obsolete, and the these other directories could also be handled: firefox/nightly/contrib (~ 4.5 GB) thunderbird/nightly/contrib (~ 8 GB) seamonkey/nightly/contrib (~ 60 GB) calendar/sunbird/nightly (~ 35 GB) calendar/lightning/nightly (~ 37 GB) In the last two directories, the Calendar folks have already made directories for 2005 and 2006 (to keep the page length down, a la bug 360397). We should check with them if they have any objections to moving these dirs over. I have most of a patch for this, just need to finish it up and do some testing before sending it Dave's way for review. We should also have a README.TXT in each directory, which explains how to find old builds on archive.m.o
Assignee | ||
Updated•17 years ago
|
Priority: -- → P3
Comment 1•17 years ago
|
||
FWIW, I think there's a cron job now which outright deletes things in the contrib directories that are older than a certain age (rather than moving them to archive)
Comment 2•17 years ago
|
||
(In reply to comment #0) > calendar/sunbird/nightly (~ 35 GB) > calendar/lightning/nightly (~ 37 GB) > > In the last two directories, the Calendar folks have already made directories > for 2005 and 2006 (to keep the page length down, a la bug 360397). We should > check with them if they have any objections to moving these dirs over. I don't have any objections, go ahead.
Assignee | ||
Comment 3•17 years ago
|
||
archive.m.o and ftp.m.o are now a single site, so this bug is no longer valid.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•