microsoft/vscode2 files

Azure Pipelines

Use when validating Azure DevOps pipeline changes for the VS Code build. Covers queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes without waiting for full CI runs.

Specification
Skill ID
microsoft/vscode/azure-pipelines
Publisher
microsoft
Repository
vscode
Installs
0
Files
2
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

microsoft/vscode/azure-pipelinesInstalls these files
  • SKILL.md
  • azure-pipeline.ts

What this skill tells the agent

Validating Azure Pipeline Changes

When modifying Azure DevOps pipeline files (YAML files in build/azure-pipelines/), you can validate changes locally using the Azure CLI before committing. This avoids the slow feedback loop of pushing changes, waiting for CI, and checking results.

Prerequisites

  1. Check if Azure CLI is installed: ``bash az --version ``

If not installed, install it:

   # macOS
   brew install azure-cli

   # Windows (PowerShell as Administrator)
   winget install Microsoft.AzureCLI

   # Linux (Debian/Ubuntu)
   curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
  1. Check if the DevOps extension is installed: ``bash az extension show --name azure-devops ``

If not installed, add it:

   az extension add --name azure-devops
  1. Authenticate: ``bash az login az devops configure --defaults organization=https://dev.azure.com/monacotools project=Monaco ``

VS Code Main Build

The main VS Code build pipeline:

  • Organization: monacotools
  • Project: Monaco
  • Definition ID: 111
  • URL: https://dev.azure.com/monacotools/Monaco/_build?definitionId=111

VS Code Insider Scheduled Builds

Two Insider builds run automatically on a scheduled basis:

  • Morning build: ~7:00 AM CET
  • Evening build: ~7:00 PM CET

These scheduled builds use the same pipeline definition (111) but run on the main branch to produce Insider releases.


Queueing a Build

Use the queue command to queue a validation build:

# Queue a build on the current branch
node .github/skills/azure-pipelines/azure-pipeline.ts queue

# Queue with a specific source branch
node .github/skills/azure-pipelines/azure-pipeline.ts queue --branch my-feature-branch

# Queue with custom parameters
node .github/skills/azure-pipelines/azure-pipeline.ts queue --parameter "VSCODE_BUILD_WEB=false" --parameter "VSCODE_PUBLISH=false"

# Parameter value with spaces
node .github/skills/azure-pipelines/azure-pipeline.ts queue --parameter "VSCODE_BUILD_TYPE=Product Build"
Important: Before queueing a new build, cancel any previous builds on the same branch that you no longer need. This frees up build agents and reduces resource waste: ``bash # Find the build ID from status, then cancel it node .github/skills/azure-pipelines/azure-pipeline.ts status node .github/skills/azure-pipelines/azure-pipeline.ts cancel --build-id <id> node .github/skills/azure-pipelines/azure-pipeline.ts queue ``

Script Options

OptionDescription
--branch <name>Source branch to build (default: current git branch)
--definition <id>Pipeline definition ID (default: 111)
--parameter <entry>Pipeline parameter in KEY=value format (repeatable); use this when the value contains spaces
--parameters <list>Space-separated parameters in KEY=value KEY2=value2 format; values must not contain spaces
--dry-runPrint the command without executing

Product Build Queue Parameters (build/azure-pipelines/product-build.yml)

NameTypeDefaultAllowed ValuesDescription
VSCODE_QUALITYstringinsiderexploration, insider, stableBuild quality channel
VSCODE_BUILD_TYPEstringProduct BuildProduct, CIBuild mode for Product vs CI
NPM_REGISTRYstringhttps://pkgs.dev.azure.com/monacotools/Monaco/_packaging/vscode/npm/registry/any URLCustom npm registry
CARGO_REGISTRYstringsparse+https://pkgs.dev.azure.com/monacotools/Monaco/_packaging/vscode/Cargo/index/any URLCustom Cargo registry
VSCODE_BUILD_WIN32booleantruetrue, falseBuild Windows x64
VSCODE_BUILD_WIN32_ARM64booleantruetrue, falseBuild Windows arm64
VSCODE_BUILD_LINUXbooleantruetrue, falseBuild Linux x64
VSCODE_BUILD_LINUX_SNAPbooleantruetrue, falseBuild Linux x64 Snap
VSCODE_BUILD_LINUX_ARM64booleantruetrue, falseBuild Linux arm64
VSCODE_BUILD_LINUX_ARMHFbooleantruetrue, falseBuild Linux armhf
VSCODE_BUILD_ALPINEbooleantruetrue, falseBuild Alpine x64
VSCODE_BUILD_ALPINE_ARM64booleantruetrue, falseBuild Alpine arm64
VSCODE_BUILD_MACOSbooleantruetrue, falseBuild macOS x64
VSCODE_BUILD_MACOS_ARM64booleantruetrue, falseBuild macOS arm64
VSCODE_BUILD_MACOS_UNIVERSALbooleantruetrue, falseBuild macOS universal (requires both macOS arches)
VSCODE_BUILD_WEBbooleantruetrue, falseBuild Web artifacts
VSCODE_PUBLISHbooleantruetrue, falsePublish to builds.code.visualstudio.com
VSCODE_RELEASEbooleanfalsetrue, falseTrigger release flow if successful
VSCODE_STEP_ON_ITbooleanfalsetrue, falseSkip tests
VSCODE_USE_LEGACY_OSS_NOTICEbooleanfalsetrue, falseKeep the legacy mixin ThirdPartyNotices.txt instead of the Component Governance notice

Example: run a quick CI-oriented validation with minimal publish/release side effects:

node .github/skills/azure-pipelines/azure-pipeline.ts queue \
   --parameter "VSCODE_BUILD_TYPE=CI Build" \
   --parameter "VSCODE_PUBLISH=false" \
   --parameter "VSCODE_RELEASE=false"

Checking Build Status

Use the status command to monitor a running build:

# Get status of the most recent builds
node .github/skills/azure-pipelines/azure-pipeline.ts status

# Get overview of a specific build by ID
node .github/skills/azure-pipelines/azure-pipeline.ts status --build-id 123456

# Watch build status (refreshes every 30 seconds)
node .github/skills/azure-pipelines/azure-pipeline.ts status --watch

# Watch with custom interval (60 seconds)
node .github/skills/azure-pipelines/azure-pipeline.ts status --watch 60

Script Options

OptionDescription
--build-id <id>Specific build ID (default: most recent on current branch)
--branch <name>Filter builds by branch name (shows last 20 builds for branch)
--reason <reason>Filter builds by reason: manual, individualCI, batchedCI, schedule, pullRequest
--definition <id>Pipeline definition ID (default: 111)
--watch [seconds]Continuously poll status until build completes (default: 30s)
--download-log <id>Download a specific log to /tmp
--download-artifact <name>Download artifact to /tmp
--jsonOutput raw JSON for programmatic consumption

Cancelling a Build

Use the cancel command to stop a running build:

# Cancel a build by ID (use status command to find IDs)
node .github/skills/azure-pipelines/azure-pipeline.ts cancel --build-id 123456

# Dry run (show what would be cancelled)
node .github/skills/azure-pipelines/azure-pipeline.ts cancel --build-id 123456 --dry-run

Script Options

OptionDescription
--build-id <id>Build ID to cancel (required)
--definition <id>Pipeline definition ID (default: 111)
--dry-runPrint what would be cancelled without executing

Testing Pipeline Changes

When the user asks to test changes in an Azure Pipelines build, follow this workflow:

  1. Queue a new build on the current branch
  2. Poll for completion by periodically checking the build status until it finishes

Polling for Build Completion

Use a shell loop with sleep to poll the build status. The sleep command works on all major operating systems:

# Queue the build and note the build ID from output (e.g., 123456)

Use this skill in a project

Open any RiverX project, search the Skills panel for microsoft/vscode/azure-pipelines, and install it in one click.

Use this skill