Closed
Bug 438600
Opened 16 years ago
Closed 16 years ago
Remove old localized Seamonkey nightlies
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: nthomas, Assigned: nthomas)
Details
Attachments
(1 file)
63.07 KB,
application/x-bzip2
|
Details |
About 125GB of space is being used on ftp.m.o by localized Seamonkey nightlies, which we don't keep for other apps (just latest-<branch>-l10n). We need to clean them up to get some breathing room
Assignee | ||
Updated•16 years ago
|
Priority: -- → P2
Summary: Remove localized Seamonkey nightlies → Remove old localized Seamonkey nightlies
Assignee | ||
Comment 1•16 years ago
|
||
Eg: in /pub/mozilla.org/seamonkey/nightly/2008: find 05 -type f ! -name '*en-US*' -ls | grep trunk | grep -v xpi | awk '{sum+=$7; printf("%9s %s\n",$7,$11)} END{ print sum/1024/1204," MB to be saved"}' | tee ~/cf/remove_seamonkey_l10n/2008-05 | less find 05 -type f ! -name '*en-US*' | grep trunk | grep -v xpi | xargs rm -v | tee -a ~/cf/remove_seamonkey_l10n/2008-05
Comment 2•16 years ago
|
||
Would it be possible to do this on a script basis for the (near) future? I think in the longer term, we will probably switch to a buildbot-based system instead of tinderbox for doing nightlies and while converting to that, we can look into rewriting the upload stuff in a way that only en-US nightlies get archived.
Assignee | ||
Comment 3•16 years ago
|
||
We could possibly do that. I just filed bug 438620 on how to fix this with tinderbox configuration, it might look like a lot but is actually pretty simple. Setting this one P3 until we decide what to do.
Priority: P2 → P3
Assignee | ||
Comment 4•16 years ago
|
||
Removed the files in 2008/06/, and setup a cronjob to auto-remove the files in seamonkey/nightly/2008/07/ (root@dm-stage01:/etc/crond.d/). I really think this is a temporary stopgap and the correct solution is to fix the tinderbox setup.
Comment 5•16 years ago
|
||
Files with what age are being removed in 07/? i.e. are the latest ones still there so the automatic update info we push up does succeed? And it's right, that's all temporary, but we need no fix in tinderbox, as SeaMonkey is working on moving to hg and 1.9.1 currently, where we'll use buildbot instead of tinderbox.
Assignee | ||
Comment 6•16 years ago
|
||
I didn't realize you were serving updates for locales so it was removing all l10n files, regardless of age. The cronjob is now adjusted to remove files more than 2 days old. You could run 20080701hh/upload-packages.sh on each tinderbox if you want to get today's files back on the ftp server.
Comment 7•16 years ago
|
||
Thanks, I think we can live with not having the builds there for a day, we're just in pre-alpha ;-)
Assignee | ||
Comment 8•16 years ago
|
||
I guess this is INVALID after the switch to mercurial. Lets do it right in buildbot.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•