Closed Bug 522528 Opened 16 years ago Closed 15 years ago

[tracking bug] automate post-clone setup of build and talos slaves

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

References

Details

(Whiteboard: [buildslaves])

Basically, we should be able to clone slaves, turn them on, and have them go straight to staging - without anybody touching them. The new process should look like this: * Turn on slave * Let slave run in staging * Move to production The initial dependent bugs are for work involved with the build slaves. Talos version to be filed later.
Depends on: 524108
Depends on: 525443
Talos 0 -> staging is being integrated with the new r3 images - adding dep bugs.
Depends on: 537748, 537836, 537750, 537751
Whiteboard: [buildslaves]
To the best of my knowledge, the Talos machines are working with buildbot-tac.py and OPSI hostkey automation (where necessary). Going to keep this bug open until we actually roll out the new machines as a verification.
No longer depends on: 537750, 537751, 537836, 537748
Depends on: 537750, 537751, 537836, 537748
(In reply to comment #2) > To the best of my knowledge, the Talos machines are working with > buildbot-tac.py and OPSI hostkey automation (where necessary). Going to keep > this bug open until we actually roll out the new machines as a verification. I think we've rolled out more machines since January. -> FIXED.
Status: ASSIGNED → 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.