Closed
Bug 771291
Opened 12 years ago
Closed 12 years ago
Figure out how to incorporate VS2012 into our w64 imaging process
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: armenzg, Assigned: armenzg)
References
Details
Eventually we will want to deploy the VS2012 RC to the Win64 slaves and incorporate to the re-imaging process.
FTR: We don't want to deploy the current RC to our slaves until there is a final version but I would like to have a script for it and perhaps have a dedicated VM where we have the files placed in.
This is what I have done:
* Download VS Professional "Product Layout File" [1] (this is a small file)
* The executable only asks for a directory to download the whole thing to. In my case I put everything on C:\Tools\VS12_RC
* I shared C:\Tools\VS12_RC from w64-ix-slave40
** I also set "Turn off password protected sharing"
* From the slave I want this installed to I do:
** run this "\\w64-ix-slave40\VS12_RC\vs_professional.exe /quiet /restart"
[1] http://www.microsoft.com/visualstudio/11/en-us/downloads#professional
Updated•12 years ago
|
Assignee: server-ops-releng → mlarrain
Comment 1•12 years ago
|
||
w64-ix-slave40.winbuild.scl1 is alerting in nagios. I presume it's not running nrpe due to the changes being made here. Please be sure to fix nagios when this machine is done being used for test purposes.
Comment 2•12 years ago
|
||
http://windowsteamblog.com/windows/b/bloggingwindows/archive/2012/08/01/windows-8-has-reached-the-rtm-milestone.aspx
The final release of VS 11 will be out August 15th.
Comment 3•12 years ago
|
||
Armen I can have MDT run that from the command line and if any files need to be placed on the system then I can also have MDT do that. Both seem relatively easy to accomplish.
Comment 4•12 years ago
|
||
passing this back to armen since I answered his questions regarding this.
Assignee: mlarrain → nobody
Component: Server Operations: RelEng → Release Engineering: Automation (Release Automation)
QA Contact: arich → bhearsum
Comment 5•12 years ago
|
||
Giving this to coop since he's taking care of the windows stuff while armen is on PTO.
Assignee: nobody → coop
Comment 6•12 years ago
|
||
Reassigning to Armen since we never got to this point while he was away.
Assignee: coop → armenzg
Assignee | ||
Comment 7•12 years ago
|
||
Today, I'm grabbing the final release of VS2012 and installing it into one of our slaves.
Once I verified I would like to ask a w64 slave to be re-image but adding the step to install VS2012 as well.
I will verify that both the w32/VS2010 and w32-metro/VS2012 builds can be generated.
This is part of adding nightly builds for the elm project.
Updated•12 years ago
|
Component: Release Engineering: Automation (Release Automation) → Release Engineering: Platform Support
QA Contact: bhearsum → coop
Assignee | ||
Updated•12 years ago
|
Priority: -- → P3
Assignee | ||
Comment 8•12 years ago
|
||
We dropped the necessity to use VS2012.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Comment 9•12 years ago
|
||
How can we enable Metro support without using VS2012?
Assignee | ||
Comment 10•12 years ago
|
||
I don't know. jimm is doing some more investigation.
If anything was to change we would reopen this bug.
Comment 11•12 years ago
|
||
(In reply to Masatoshi Kimura [:emk] from comment #9)
> How can we enable Metro support without using VS2012?
Back port the widget back end to vs10 (bug 794983), figure out how to use the 8.0 sdk with normal builds (bug 774910), and anything else that comes up along the way.
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•