Closed Bug 564230 Opened 15 years ago Closed 15 years ago

Setup 10 new osx10.5 talos slaves

Categories

(Release Engineering :: General, defect, P2)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: joduinn, Assigned: joduinn)

References

Details

(Whiteboard: [buildslaves][talos][unittest])

Attachments

(1 file)

adds leopard slaves to production-puppet
(deleted), patch
jhford
: review+
jhford
: checked-in+
Details | Diff | Splinter Review
This is to track: 1) Add talos-r3-leopard-{041...050}.build.mozilla.org to staging and production master configs. They will all run in staging first, but we should keep 5 in staging. 2) Add all to graphserver.
Summary: Setup 10 new osx10.5 buildslaves → Setup 10 new osx10.5 talos slaves
All being worked on now, or very soon.
Priority: -- → P2
So 041-050 apparently got added to production, but have now been removed from that (bug 564658) pending confirmation that puppet is working reliably. When adding new machines to production please leave a comment in the appropriate RelEng bug to help those that are location-challenged.
Actually, I can't reach 050. Did that one get racked yet ?
Whiteboard: [buildslaves][talos][unittest]
(In reply to comment #5) > Actually, I can't reach 050. Did that one get racked yet ? ping, on this.
All except 050 are connected to tm02
(In reply to comment #7) > All except 050 are connected to tm02 buildbot.tac was pointing to the wrong master. 050 is now fixed, and all the rest are already online, so all done here.
Assignee: nobody → joduinn
Status: NEW → RESOLVED
Closed: 15 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: