Closed Bug 510604 Opened 13 years ago Closed 13 years ago
Setup 10 new linux buildslaves with buildbot
Once the VMs are created, we'll need to do manual setup, and get buildbot slave running in staging, then move to production. This bug is to track the RelEng setup work.
Joel: Did you run unittests on Fennec desktop with Maemkit, or without?
Aki, You don't need maemkit, but it helps for crashes that occur in mochitest.
We really need these on pm02, and a couple on pm01 - how's this coming Aki?
Oops, grabbed this before they were ready and then this fell off my radar. I'll do this today.
Two things: - Adding them to both staging and production in this patch. Can split them out to two patches if necessary, but I thought this would be more expedient. - Changed the mozilla2/config.py slave settings to use ranges rather than a long list of slave numbers, which I think is easier to read/edit, but I can change it back if need be.
Attachment #398169 - Flags: review?(bhearsum)
Attachment #398168 - Flags: review?(bhearsum) → review+
Attachment #398169 - Flags: review?(bhearsum) → review+
Attachment #398168 - Flags: checked-in+
Comment on attachment 398169 [details] [diff] [review] add slaves to buildbot-configs revision 1475:1c444029c5c5
Attachment #398169 - Flags: checked-in+
running in staging. these were failing until i updated the staging keys; letting this run overnight.
Looks like these slaves don't have the new gcc. I don't know why puppet isn't taking care of it.
looks like the new slaves are unable to mount the NFS share that has most of the puppet files. I'm looking into it with IT.
p-m: moz2-linux-slave26 moz2-linux-slave27 p-m2: moz2-linux-slave28 moz2-linux-slave29 moz2-linux-slave30 moz2-linux-slave31 moz2-linux-slave32 moz2-linux-slave33 moz2-linux-slave34 moz2-linux-slave35 watching these.
Status: NEW → RESOLVED
Closed: 13 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.