Skip to content
This repository has been archived by the owner on Aug 8, 2024. It is now read-only.

Latest commit

 

History

History
76 lines (48 loc) · 4.15 KB

INTERNAL.md

File metadata and controls

76 lines (48 loc) · 4.15 KB
Raw

Links for internal team members to find build definitions, etc.

Note that usually only the most recent link in each section is interesting. Older links are included for reference only.

PR Build Definition

The PR build definition can be found here or by navigating through an existing PR.

Signed Build Definitions

VS 16.4 to current

VS 15.7 to 16.3

VS 15.6

VS 15.0 to 15.5

Branch auto-merge definitions

Branch auto-merge definitions are specified here.

VS Insertion Generators

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.3

VS 16.2

VS 16.1

VS 16.0 and prior were done manually

VS Insertions as part of the build definition

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.

Less interesting links

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.5.0.0-beta.* package from the specified build to NuGet. This should be run every time a new SDK preview is released.

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.

MyGet package uploader. Uploads various packages for internal consumption. Feed URL is https://dotnet.myget.org/F/fsharp/api/v3/index.json.

Internal source mirror.