Audit Mac ref platform and check production machines

RESOLVED WORKSFORME

Status

Release Engineering
General
P3
normal
RESOLVED WORKSFORME
11 years ago
4 years ago

People

(Reporter: joduinn, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

1) We should check that all our production mac machines are using the current ref platform.

2) We should decide if we want to update/refresh the mac ref platform, like we have recently done for linux, win32.
Priority: -- → P3
Depends on: 391772
Assignee: build → nobody
QA Contact: mozpreed → build

Updated

10 years ago
Assignee: nobody → ccooper
I'd like the unittest machines (qm-xserve02, qm-stage-osx-01) to the list of machines to be audited. Not sure how we resolve variations between build and unittest, but we should probably address that problem sooner rather than later.

Updated

10 years ago
Assignee: ccooper → nobody
sorry for polluting this. disregard request to audit unittest machinery. We can do that in a separate bug.
in triage:

1) not touching mozilla1.8 

2) mozilla1.9: we're counting firefox mac builder as official ref standard. Need to compare thunderbird, xulrunner mac builder to make sure they are the same.

3) mozilla2 macs are confirmed to be identical, as they are all imaged from each other.

(In reply to comment #3)
> 2) mozilla1.9: we're counting firefox mac builder as official ref standard.
> Need to compare thunderbird, xulrunner mac builder to make sure they are the
> same.
Thunderbird builder going offline now, as they are moving to hg. Only XULrunner mac builder left to check here.


Component: Release Engineering → Release Engineering: Future
QA Contact: build → release

Updated

9 years ago
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME

Comment 5

8 years ago
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.