Skip to content

Latest commit

 

History

History
36 lines (21 loc) · 1.7 KB

INTERNAL.md

File metadata and controls

36 lines (21 loc) · 1.7 KB
Raw

Links for internal team members.

PR Build Definition

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

Signed Build Definition

Signed build definition

NuGet Package Upload

NuGet packages produced from every build of main are auto-published to the NuGet feed https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json

Publish VS Code Extension

A new version of the VS Code extension can be published with this release definition. You'll have to select the appropriate passing build to publish. This is a one-step process. Once submitted, the new extension will appear in the VS Code Marketplace in about 10 minutes once their internal validations are complete.

The publish/verification script is located in this repo at eng/publish/PublishVSCodeExtension.ps1.

Rolling back to an older version of the VS Code Extension

To roll back to a previous build, you'll need to:

  1. Find the build you'd like to roll back to.
  2. Copy the commit's SHA.
  3. Start a new signed build with that SHA.
  4. Use that build to publish like normal.

This ensures that the version number of the extension is always increasing to pass the VS Code Marketplace verification.

Internal Code Mirror

The public GitHub code is internally mirrored here to enable signed builds. You'll likely never need to do anything with this.