Closed
Bug 395795
Opened 17 years ago
Closed 17 years ago
Create Win32 VM with VMI client installed for group use
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: joduinn, Unassigned)
Details
To maintain the different VMs, we need to use VMI. Some people have created private VMs to run the VMI client. Instead of each member of build group having to setup & maintain their own installation in their own VM, it seems better to have one VM-running-VMI shared across the group, and one shared set of docs on how to use it. (At least some of those private VMs also have private files on them, and are also used for non-shared work, hence looking for a new clean VM explicitly just for sharing.)
Reporter | ||
Updated•17 years ago
|
Priority: -- → P3
Comment 1•17 years ago
|
||
Slightly confused here: are you saying we should have a shared VM, and we all use RDB/VNC/etc. to access that VM to use VI, or have a reference copy of a VM that we can all use on our own laptops/workstations/etc.?
Reporter | ||
Comment 2•17 years ago
|
||
"a shared VM, and we all use RDB/VNC/etc. to access that VM to use VI"
Reporter | ||
Comment 3•17 years ago
|
||
Discussed in Build meeting yesterday. Conclusion is that people prefer having their own VMware image, running their own installation of VMI. Closing as WONTFIX.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
Updated•17 years ago
|
Assignee: build → nobody
QA Contact: mozpreed → build
Assignee | ||
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
•