Closed
Bug 388366
Opened 17 years ago
Closed 17 years ago
Create win32 buildbot slave VM by copying pacifica-vm
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Assigned: joduinn)
References
Details
To test build automation, we need a win32 buildbot slave. This needs to run in a VM which contains the exact same bits as we currently use in pacifica-vm. Once the new VM is copied and running, we can add buildbot slave config files and see what happens! I'd like to call this VM "bld-win-slave01".
Assignee | ||
Updated•17 years ago
|
Assignee: build → joduinn
Priority: -- → P2
Updated•17 years ago
|
Assignee: joduinn → rhelmer
Updated•17 years ago
|
Whiteboard: ETA July 17th
Updated•17 years ago
|
Whiteboard: ETA July 17th → cloning disk, ETA Jul 18
Comment 1•17 years ago
|
||
"staging-pacifica-vm" installed as per irc discussion about hostnames. Buildbot is not set up, instructions for win32 are at: http://wiki.mozilla.org/ReferencePlatforms/BuildBot/Win32
Assignee: rhelmer → joduinn
Updated•17 years ago
|
Whiteboard: cloning disk, ETA Jul 18
Assignee | ||
Updated•17 years ago
|
Blocks: end2end-bld
Assignee | ||
Comment 2•17 years ago
|
||
staging-pacifica-vm.build.mozilla.org is now running buildbot slave "win32-slave1". This slave is connecting to buildbot master on staging-prometheus-vm, doing builds to completion, and showing green on buildbot master.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•