431451 - setup Mac unit/mochi/crash/reftest buildbot slave for SeaMonkey

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Robert Kaiser]

This is a followup to bug 416469 for the Mac part of that bug, Linux and Windows VMs were created and set up in the other bug.

What we still would need now is a Mac box to run a buildbot slave for SeaMonkey unit tests.

Comment 1

[[e-mail] (:bhearsum)]

This should go to Server ops.

Comment 2

[Robert Kaiser]

OK, to server ops per Ben.

Comment 3

[matthew zeier [:mrz]]

Er, which Mac box?  Does Rel. Eng. have a box I should use for this?

Comment 4

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

This should be a community mac box, as I understand it. Not sure how many macs are available community right now, but cc'ing Seth. 

Comment 5

[matthew zeier [:mrz]]

There aren't currently any spare Macs in inventory (not counting the two "QA" Xserves).  

Is this something Seth is going to provide?

Comment 6

[Seth Bindernagel]

I don't have any formal requests in the queue for this issue.  But, it's clear we need a Mac box for this.  Let me discuss and will respond here.

Comment 7

[Seth Bindernagel]

Spoke to Mike Shaver.  Let's move forward with this request.  MRZ, can you set up a new Mac Mini for the SeaMonkey community to use for unit/mochi/crash/reftest buildbot slave.  Thanks.

Comment 8

[matthew zeier [:mrz]]

Will a fresh install of 10.5.2 work or is there some build Mac Mini ref image you want?

Comment 9

[Robert Kaiser]

Seth, thanks for getting this soltuion.

mrz, I think 10.5.2 sounds good, anything that can (or even has all the stuff to) run unit test buildbots should be fine.

Comment 10

[matthew zeier [:mrz]]

Over to Justin for ordering.

Comment 11

[Justin Fitzhugh]

in stock - handed to mrz or mark for deployment.

Comment 12

[matthew zeier [:mrz]]

cb-sea-miniosx01.sj.mozilla.com / 63.245.210.27

I grabbed your ssh keys out of LDAP and put you into root's authorized_keys file.  You should be able to change user account passwords and VNC in.  If you get stuck, please file another bug.