Closed Bug 458842 Opened 16 years ago Closed 16 years ago

Move tinderbox for Mac/XULRunner/Mozilla1.9.0 builds from bm-xserve07 to 08

Categories

(Release Engineering :: General, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Assigned: nthomas)

Details

Attachments

(1 file)

bm-xserve07 used to do Thunderbird and XULRunner builds on the CVS trunk, using tinderbox. Now it does Thunderbird from {mozilla,comm}-central using buildbot, and is administered by Mozilla Messaging, so it makes sense to move the XULRunner build to somewhere else.

bm-xserve08 is doing nightlies/hourlies for Firefox 3.0.x and is the same vintage as 07. We can spare 11 minutes for the occasional XULRunner hourly, and 30 minutes for a nightly, given Fx3.0 is in maintenance mode.

This bug is about setting adding the XULRunner config on bm-xserve08, and cleaning up 07.
Priority: -- → P2
File 	Rev
mozilla/tools/tinderbox-configs/xulrunner/macosx/mozconfig 	1.4
mozilla/tools/tinderbox-configs/xulrunner/macosx/tinder-config.pl 	1.8
Gozer, your build logs would be massively shorter if you remove the -v here
 http://hg.mozilla.org/build/buildbot-configs/file/8a20c6eae8e6/thunderbird/master.cfg#l576
Huh, we do that too. That's silly.

In other news, I've removed aus* and cltbld* from bm-xserve07:~cltbld/.ssh/, because it doesn't look like they're being used.
Test build was successful on bm-xserve08, so I've added the xulrunner config to /builds/tinderbox/multi-config.pl and HUP'd the multi-tinderbox process. Will remove files from bm-xerve07 and close this once I see more builds on the XULRunner tree.
bm-xserve08 is reporting as expected to XULRunner tree. I've removed bm-xserve07:/builds/tinderbox/XR-Trunk/Darwin_8.8.4_Depend but left the rest.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
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: