Note that usually only the most recent link in each section is interesting. Older links are included for reference only.
The PR build definition can be found here or by navigating through an existing PR.
VS 16.4 to current - part of the build definition. See below.
The following insertion generators are automatically invoked upon successful completion of a signed build in each of their respective branches.
VS 16.0 and prior were done manually
Starting with the 16.4 release and moving forwards, the VS insertion is generated as part of the build. The relevant
bits can be found near the bottom of azure-pipelines.yml under the VS Insertion header. The
interesting parameters are componentBranchName and insertTargetBranch. In short, when an internal signed build
completes and the name of the branch built exactly equals the value in the componentBranchName parameter, a component
insertion into VS will be created into the insertTargetBranch branch. The link to the insertion PR will be found
near the bottom of the build under the title 'Insert into VS'. Examine the log for 'Insert VS Payload' and near the
bottom you'll see a line that looks like Created request #xxxxxx at https://....
To see all insertions created this way (possibly including for other internal teams), check here.
Nightly VSIX (master) uploader. Uploads
a package from every build of master to the Nightly VSIX feed.
Nightly VSIX (preview) uploader. Uploads a package from every build of the branch that corresponds to the current Visual Studio preview to the Preview VSIX feed.
MyGet package uploader. Uploads various
packages for internal consumption. Feed URL is https://dotnet.myget.org/F/fsharp/api/v3/index.json.