Closed Bug 495948 Opened 16 years ago Closed 16 years ago

deploy OPSI client software on production win32 build slaves

Categories

(Release Engineering :: General, defect, P3)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

References

Details

Machines to deploy it on: win32-slave01, 02, 05 -> 29, try-win32-slave01 -> 19, win32 ref platform Instructions can be found here: https://wiki.mozilla.org/index.php?title=ReferencePlatforms/Win32&oldid=137845#OPSI_Client_.26_Autoit
Blocks: 491298
Priority: -- → P3
No longer blocks: 474572
Blocks: 474572
Does the OPSI deployment depend on the machine rename, or the rename depend on the deployment?
OPSI depends on the rename, of course.
No longer blocks: 491298
Depends on: 491298
No longer depends on: 491298
Depends on: 491298
the OPSI client has been deployed on win32-slave01, 02, 05 -> 20, and 23 -> 29 03, 04, and 21 are staging slaves which already have it. The only class in this group that still needs it is slave 22, which will be done when it becomes idle. Tomorrow we'll do the deployment onto the try slaves, assuming bug 497092 is resolved by then.
slave22 has opsi now, only the try slaves left.
Depends on: 497422
try slaves all have opsi on them now. only thing left is the ref platform, which will bed one on monday.
We're all done here, finally. All production slaves have OPSI (try+moz2-*), as well as the ref platform.
Status: ASSIGNED → RESOLVED
Closed: 16 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.