Windows Installer machine needed for MSVC

[partouf]

Need a throw-away instance that we can start each time we want to package a new MSVC version.

Scripts in https://github.com/compiler-explorer/infra/tree/main/msvc-install were used to get a lot of versions, but is obviously not recommended for normal use.

Idea is to:

• launch a fresh instance
• pass the URL to an install script (called from a manual workflow?)
• it downloading the installer from that url
• install the buildtools
• rename the msvc compiler dir to $compilerVersion-$productVersion
• zip up that directory
• upload to s3
• shutdown

Possible problems:

• We'll only know the productVersion after the compiler has been installed (productVersion is unique, compilerVersion is not)
• So only after it's know you could use msvc-install/gen-props.ps1 to see how the properties would look
• probably much more...

[mattgodbolt]

Looking for what "the URL" is here currently :) MS's website is... not helpful here

[mattgodbolt]

We might be able to coerce packer into doing all this for us. Will dig about.

Update: Mayybe; we can make it skip_create_ami: true to skip making the AMI, and then get it to upload the ZIP to S3 directly. We'd be using packer as a "convenient" way to fire up an AMI, run something, and then shut it down only. That might be ok?

[partouf]

2022 https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-history
2019 https://learn.microsoft.com/en-us/visualstudio/releases/2019/history
2017 https://learn.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes-history

Urls are the buildtools installers

Preview https://aka.ms/vs/17/pre/vs_BuildTools.exe

[mattgodbolt]

Thanks!

[mattgodbolt]

Partly done. Will leave this open til we're happy with it.