Closed Bug 494325 Opened 16 years ago Closed 16 years ago

Setup bm-xserve11 for main builder pool

Categories

(Release Engineering :: General, defect, P3)

Product:
Release Engineering
Component:
General
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nthomas, Assigned: nthomas)

References

Details

Attachments

(1 file)

Add bm-xserve11 to production and staging master
1.51 KB, patch
mozilla
: review+
nthomas
: checked-in+
Details | Diff | Splinter Review
After this machine gets a reimage (bug 474544), we should bring it up to reference doc standard (like bug 474544). It can get tested on the staging-master then go into production to give us another xserve in the pool.
Oops, reimage is in bug 493928.
Assignee: nobody → nthomas
Priority: -- → P2
Attachment #380292 - Flags: review?(aki) → review+
Turns out the ref image from bm-xserve22 was not up to date (XCode 3.0 etc). I've updated bm-xserve11 to spec and we'll take a new ref image from it, but first I want to connect it up to staging-master and do some builds to make sure it survives the load OK.
Comment on attachment 380292 [details] [diff] [review] Add bm-xserve11 to production and staging master staging part landed as committed changeset 1174:afe09369a91b
Worked fine in staging. Now idle while we create a new xserve image from it, by reopening bug 494791.
Depends on: 494791
Priority: P2 → P3
Comment on attachment 380292 [details] [diff] [review] Add bm-xserve11 to production and staging master production part landed as: committed changeset 1183:5718da1ab838
Attachment #380292 - Flags: checked‑in+
Now connected to production-master, waiting for a few cycles before resolving.
Working well, --> FIXED.
Status: NEW → 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

Creator:
Created:
Updated:
Size: