Closed Bug 390340 Opened 18 years ago Closed 17 years ago

Revive l10n builds

Categories

(Release Engineering :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Assigned: nthomas)

References

Details

Attachments

(1 file)

We're currently lacking some l10n coverage due to machine failures and release activity. Here's the plan for getting back in action: cerberus-vm - re-enable builds (win32: Fx/Tb-Trunk, Fx/Tb-Mozilla1.8) karma - re-enable builds (linux: Fx/Tb-Mozilla1.8) xserve05 (died) - move Mozilla1.8 builds to xserve02 (mac: Fx/Tb-Mozilla1.8) - move Trunk builds to xserve07 (mac: Fx/Tb-Trunk) l10n-win32-tbox - set up new ref image (linux: Fx/Tb-Trunk)
Priority: -- → P2
(In reply to comment #0) > cerberus-vm - re-enable builds (win32: Fx/Tb-Trunk, Fx/Tb-Mozilla1.8) > karma - re-enable builds (linux: Fx/Tb-Mozilla1.8) Done.
> xserve05 (died) - move Mozilla1.8 builds to xserve02 (mac: Fx/Tb-Mozilla1.8) > - move Trunk builds to xserve07 (mac: Fx/Tb-Trunk) The first is done, on the basis of building Fx, Tb, Fx-l10n, Tb-l10n, then Fx, Tb a couple more times. I didn't want to use --interval when the same box is doing performance tests fof Firefox. I had some issues with old mozconfigs for Trunk, and will work on that tomorrow (pending other tasks).
l10n-linux-tbox is now providing coverage for Firefox & Thunderbird l10n on the Trunk. Still working on getting a Mac and setting it up; win32 ref platform is not too far off, we'll deploy it for en-US first.
These are the changes I needed to get l10n working on Intel Mac's and the CentOS 5 ref platform. There is also a bunch of comment culling in the mozconfigs. Please sanity check :-)
Attachment #276840 - Flags: review?(ccooper)
Comment on attachment 276840 [details] [diff] [review] Config changes for updated tinderboxes lol, as if the header was still for boomer.
Attachment #276840 - Flags: review?(ccooper) → review+
Mac builds now cycling on Mozilla-l10n tree, it'd be great if localisers could take a look at them. I'm using a depend build (rather than a clobber), so it'd be useful to confirm that l10n checkins get picked up properly in builds. Next up, cloning the new windows ref platform.
Update: the new windows ref-platform is about a week away from completion, then a day or so to get it set up (assuming that the move to MSYS doesn't cause major headaches). (In reply to comment #3) > The first is done, on the basis of building Fx, Tb, Fx-l10n, Tb-l10n, then Fx, > Tb a couple more times. I didn't want to use --interval when the same box is > doing performance tests fof Firefox. Paul pointed out that interval is quite safe to use as builds are done sequentially, so I've adjusted the multi-config.pl for bm-xserve02. It can be paraphrased as Fx en-US Fx l10n every 8 hours Tb en-US Tb l10n every 8 hours (all 1.8 branch builds).
win32 ref platform is now done and I've set up a new tinderbox based on it. Preliminary tests runs indicate that l10n builds work just fine on MSYS, current cycle time about 35 minutes. I'm away for a few days but will finish this when I get back.
Whiteboard: ETA: 13-Sep
win32 box is now building Firefox & Thunderbird, leaving this open until I do some checks on the builds. I know that line-endings have changed from Windows to Unix in files like README.txt.
Depends on: 351476
Whiteboard: ETA: 13-Sep → waiting on 351476 for line-endings fix
Bug 351476 landed on the trunk a few days ago and I've verified that README.txt and LICENCE have DOS line-endings in win32 locales. As all three platforms are cycling quite happily I'm going to call this done. Please file a new bug for any follow-up issues.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Whiteboard: waiting on 351476 for line-endings fix
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: