Closed Bug 487636 Opened 15 years ago Closed 15 years ago

Create 6 new win32 buildbot slaves for Moz2/3.next pool

Categories

(Release Engineering :: General, defect, P3)

x86
Windows 2000
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Assigned: joduinn)

References

Details

Attachments

(2 files, 2 obsolete files)

Now that the 6 VMs are created in bug#485884, we'll need to setup buildbot
slaves running on these VMs, and add them to the buildbot master.cfg, so they'll start getting work assigned to them.
Assignee: nobody → joduinn
Now running in staging are:

moz2-win32-slave24
moz2-win32-slave25

...still working on the others.
Now running in staging are:

moz2-win32-slave24
moz2-win32-slave25
moz2-win32-slave26
moz2-win32-slave27
moz2-win32-slave28
moz2-win32-slave29

Will let them bake on staging over weekend before moving to production pool-of-slaves. fyi: so far slave24/25 have been doing builds/unittests just fine.
OS: Mac OS X → Windows 2000
Priority: -- → P2
slaves still baking in staging, but might as well get this landed so we can switch them over to production as they are ready.
Attachment #372109 - Flags: review?(bhearsum)
...this time with the *correct* attachment. Sorry for the noise.
Attachment #372109 - Attachment is obsolete: true
Attachment #372111 - Flags: review?(bhearsum)
Attachment #372109 - Flags: review?(bhearsum)
Comment on attachment 372111 [details] [diff] [review]
add new slaves to production pool-of-slaves

This is fine, but please add them to the staging config, too.
Attachment #372111 - Flags: review?(bhearsum) → review+
Depends on: 488240
similar patch for staging-master configs...
Attachment #372552 - Flags: review?(bhearsum)
(In reply to comment #5)
> (From update of attachment 372111 [details] [diff] [review])
> This is fine, but please add them to the staging config, too.

urgh... can you land this reviewed patch, and then reconfig production-master, so these new win32 slaves can be seen in production and assigned jobs.
After running nicely in staging since Friday, I've now updated these win32 slaves for production use (using new ssh keys, production-master).

moz2-win32-slave24
moz2-win32-slave25
moz2-win32-slave26
moz2-win32-slave27
moz2-win32-slave28
moz2-win32-slave29

All six slaves are currently waiting for the above master.cfg changes to be landed, and then for the master to be re-configed. All the slave setup work is done. Keeping this bug open until the production master changes are live.
Priority: P2 → P3
Comment on attachment 372111 [details] [diff] [review]
add new slaves to production pool-of-slaves

committed changeset 1092:759d250952c7
Attachment #372111 - Flags: checked‑in+
reposting patch, as nthomas spotted some diffs from the "production" patch accidentally included in this "staging" patch.
Attachment #372552 - Attachment is obsolete: true
Attachment #372566 - Flags: review?(bhearsum)
Attachment #372552 - Flags: review?(bhearsum)
production-master reconfig'd to pick up attachment 372111 [details] [diff] [review].
All 6 win32 slaves now running nicely in production - thanks Nick! I'll leave this bug open until after review of the equivalent staging patch.
Attachment #372566 - Flags: review?(bhearsum) → review+
Comment on attachment 372566 [details] [diff] [review]
add new slaves to staging pool-of-slaves

changeset:   1093:e022c8818673
Attachment #372566 - Flags: checked‑in+
All done.
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

Created:
Updated:
Size: