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.
There is also a duplicate scouting PR build that is identical to the normal PR build except that it uses a different Windows machine queue that always has the next preview build of Visual Studio installed. This is to hopefully get ahead of any breaking API changes. That build definition is here.
Branch auto-merge definitions are specified here.
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://....
Insertions generated to any rel/* branch will have to be manually verified and merged, and they'll be listed
here.
Note that insertions for other teams will also be listed.
Insertions to any other VS branch (e.g., main) will have the auto-merge flag set and should handle themselves, but
it's a good idea to check the previous link for any old or stalled insertions into VS main.
FSharp.Core (Official NuGet Release).
Uploads the final FSharp.Core package from the specified build to NuGet. This should only be run when we know for
certain which build produced the final offical package.
FSharp.Core (Preview NuGet Release).
Uploads the preview FSharp.Core.*-beta.* package from the specified build to NuGet. This should be run every time
a new SDK preview is released.
FCS (Official NuGet Release).
Uploads the final FSharp.Compiler.Service package from the specified build to NuGet. Only builds from the release/fcs
branch can be selected. This should only be run when we're fairly certain that the package is complete.
FCS (Preview NuGet Release).
Uploads the preview FSharp.Compiler.Service.*-preview.* package from the specified build to NuGet. Only builds from the
main branch can be selected. This can be run whenever we think we're ready to preview a new FCS build.
Nightly VSIX (main) uploader. Uploads
a package from every build of main 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.