arcade: Image with VS 17.6 preview 2 fails to build

Problem

Seems like we fail to install the VS workloads when generating the image.

Log: Do not Post SAS urls on github Build: https://dnceng.visualstudio.com/internal/_build/results?buildId=2135411&view=results Change: https://dnceng.visualstudio.com/internal/_git/dotnet-helix-machines/commit/a86dd4971e392335135f8f56a77dad56bd1fb16c

To be done

Install a fresh VS locally in a VM/Sandbox and then trying the scripts from helix-machines to install the VS workloads like in the logs to see which of the workloads have changed and are failing to install. Maybe install them one by one or get more logs out of that.

This issue is blocking
- Blocking updates of non-base images.
- Specifically, blocking ‘main’ builds of the dotnet-helix-machines-ci pipeline
This issue is causing unreasonable pain

Release Note Category

Feature changes/additions
Bug fixes
Internal Infrastructure Improvements

Release Note Description

Skip VS 17.6 preview2 entirely

leave vs2022 preview and scouting queues at 17.6 preview1 until preview3 is released
avoid the https://developercommunity.visualstudio.com/t/Visual-Studio-176-Preview-2-Installer-b/10318419 installer bug

About this issue

Original URL
State: closed
Created a year ago
Comments: 48 (39 by maintainers)

Most upvoted comments

For everyone else, I completed my “one or two at at time” installation work using the command line. This helped me confirm there is not an issue w/ any component or workload in our list of requirements. About the only other oddity I noticed was the --remove Component.IncredibuildMenu --remove Component.Incredibuild parts of the logged command aren’t necessary; neither component is visible in an exported .vsconfig file after doing all the --add bits and both are optional under every workload where they’re mentioned in https://learn.microsoft.com/en-ca/visualstudio/install/workload-component-id-vs-enterprise?view=vs-2022.

At this point, the main action for you all is to point me toward the right place to update the scripting that currently uses --wait.

dougbu on Mar 23, 2023