946859 - Please install VS2012 on ix-mn-w0864-001 via GPO

Status: RESOLVED FIXED

(Infrastructure & Operations :: RelOps: General, task)

Description

[John Hopkins (:jhopkins)]

We'd like to do testing of Visual Studio 2012 based builds in a staging environment.

Can you please install VS2012 on ix-mn-w0864-001 via GPO (in a supportable way in case we end up deploying it in production)?

Comment 1

[Mark Cornmesser [:markco]]

jhopkins: Will this be just a default install? 

Also if I get this done this week, should I go ahead and pushed it out to w0864-001?

Comment 2

[John Hopkins (:jhopkins)]

Yes, just a default install.  VS2010 was also a default install, right?

You can push to w0864-001 but nothing else for now.  Thanks

Comment 3

[Mark Cornmesser [:markco]]

With 2010 we broke the install to remove Microsoft F# components. I am not sure if it is included in 2012. If it is should i remove it from the install? The difference is a standard install should take  little time to roll into a gpo. However, removing a component, and rolling it into a gpo may take a bit longer.

Comment 4

[John Hopkins (:jhopkins)]

If F# is included in VS2012, let's not install it.  I'm not sure whether this is strictly necessary, but it will at least save on disk space and lower the surface area of our installed software.

Comment 5

[Mark Cornmesser [:markco]]

w0864-001 has been moved to the tester OU. After the GPO is picked up it will take a some time (less than an hour) and a few reboots before the application install competes.

Comment 6

[John Hopkins (:jhopkins)]

Attachment: WINNT 5.2 mozilla-beta leak test build failure after VS2012 installed

All staging build jobs are failing on ix-mn-w0864-001 since VS2012 was installed.  Since no buildbot config changes were made, it appears the VS2012 install has impacted functioning of the VS2010 install.

This page points at some possible solutions:

 http://stackoverflow.com/questions/10888391/error-link-fatal-error-lnk1123-failure-during-conversion-to-coff-file-inval

Comment 7

[Mark Cornmesser [:markco]]

I have been looking into to see what VS2012 could have change win the VS2010 installation. 

So far it appears that the VS2012 install touches numerous files under:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\

It also touches:
C:\ProgramData\Microsoft\VisualStudio\10.0\1033\ResourceCache.dll

Comment 8

[Mark Cornmesser [:markco]]

Where do we want to go from here on this? Do we want to reimage the machine so that it only has VS2010 and isn't failing jobs, troubleshoot the current condition and see if we can get to work as is, or do we want to put time into the VS2012 GPO install to try to have it install VS2012 independent of VS2010 completely?

Comment 9

[John Hopkins (:jhopkins)]

I'm not worried about this particular machine failing jobs as it's only doing staging builds.

Can you please install Visual Studio 2010 Service Pack 1?

Comment 10

[Mark Cornmesser [:markco]]

VS2010 has been uninstalled and reinstalled on w0864-001.

Comment 11

[John Hopkins (:jhopkins)]

Builds are failing with the same error message as in comment 6.

Comment 12

[Mark Cornmesser [:markco]]

My bad. I assumed that the current version on VS2010 we were using was SP1. It turns out it is now. I am working on getting SP1. Once i have it I can uninstall and reinstall the correct version.

Comment 13

[Mark Cornmesser [:markco]]

VS2010 SP1 is now installed on w0864-001. Hopefully this solves the issue that is causing the failing builds. If not we may need to get a bit creative.

Comment 14

[John Hopkins (:jhopkins)]

Thanks - a compile job passed as a result!

Comment 15

[John Hopkins (:jhopkins)]

Note: Due to the pre-VS2010 SP1 bustage above caused by the VS2012 install, we will have to pay special attention to the output produced by VS2010 in case there are other, more subtle problems introduced.