DiscordSign up
SKILLS.SH

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…

INSTALLATION
npx skills add https://github.com/microsoft/vscode --skill azure-pipelines
Run in your project or agent environment. Adjust flags if your CLI version differs.

SKILL.md

$27

Linux (Debian/Ubuntu)

curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash

2. **Check if the DevOps extension is installed**:

az extension show --name azure-devops


If not installed, add it:

az extension add --name azure-devops


- **Authenticate**:

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](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](https://github.com/microsoft/vscode/blob/HEAD/.github/skills/azure-pipelines/./azure-pipeline.ts) 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:

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

Option
Description

`--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-run`
Print the command without executing

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

Name
Type
Default
Allowed Values
Description

`VSCODE_QUALITY`
string
`insider`
`exploration`, `insider`, `stable`
Build quality channel

`VSCODE_BUILD_TYPE`
string
`Product Build`
`Product`, `CI`
Build mode for Product vs CI

`NPM_REGISTRY`
string
`https://pkgs.dev.azure.com/monacotools/Monaco/_packaging/vscode/npm/registry/`
any URL
Custom npm registry

`CARGO_REGISTRY`
string
`sparse+https://pkgs.dev.azure.com/monacotools/Monaco/_packaging/vscode/Cargo/index/`
any URL
Custom Cargo registry

`VSCODE_BUILD_WIN32`
boolean
`true`
`true`, `false`
Build Windows x64

`VSCODE_BUILD_WIN32_ARM64`
boolean
`true`
`true`, `false`
Build Windows arm64

`VSCODE_BUILD_LINUX`
boolean
`true`
`true`, `false`
Build Linux x64

`VSCODE_BUILD_LINUX_SNAP`
boolean
`true`
`true`, `false`
Build Linux x64 Snap

`VSCODE_BUILD_LINUX_ARM64`
boolean
`true`
`true`, `false`
Build Linux arm64

`VSCODE_BUILD_LINUX_ARMHF`
boolean
`true`
`true`, `false`
Build Linux armhf

`VSCODE_BUILD_ALPINE`
boolean
`true`
`true`, `false`
Build Alpine x64

`VSCODE_BUILD_ALPINE_ARM64`
boolean
`true`
`true`, `false`
Build Alpine arm64

`VSCODE_BUILD_MACOS`
boolean
`true`
`true`, `false`
Build macOS x64

`VSCODE_BUILD_MACOS_ARM64`
boolean
`true`
`true`, `false`
Build macOS arm64

`VSCODE_BUILD_MACOS_UNIVERSAL`
boolean
`true`
`true`, `false`
Build macOS universal (requires both macOS arches)

`VSCODE_BUILD_WEB`
boolean
`true`
`true`, `false`
Build Web artifacts

`VSCODE_PUBLISH`
boolean
`true`
`true`, `false`
Publish to builds.code.visualstudio.com

`VSCODE_RELEASE`
boolean
`false`
`true`, `false`
Trigger release flow if successful

`VSCODE_STEP_ON_IT`
boolean
`false`
`true`, `false`
Skip tests

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](https://github.com/microsoft/vscode/blob/HEAD/.github/skills/azure-pipelines/./azure-pipeline.ts) 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

Option
Description

`--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

`--json`
Output raw JSON for programmatic consumption

## Cancelling a Build

Use the [cancel command](https://github.com/microsoft/vscode/blob/HEAD/.github/skills/azure-pipelines/./azure-pipeline.ts) 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

Option
Description

`--build-id <id>`
Build ID to cancel (required)

`--definition <id>`
Pipeline definition ID (default: 111)

`--dry-run`
Print what would be cancelled without executing

## Testing Pipeline Changes

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

- **Queue a new build** on the current branch

- **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)

node .github/skills/azure-pipelines/azure-pipeline.ts queue

Poll every 60 seconds until complete (works on macOS, Linux, and Windows with Git Bash/WSL)

Replace <BUILD_ID> with the actual build ID from the queue command

while true; do

node .github/skills/azure-pipelines/azure-pipeline.ts status --build-id <BUILD_ID> --json 2>/dev/null | grep -q '"status": "completed"' &#x26;&#x26; break

sleep 60

done

Check final result

node .github/skills/azure-pipelines/azure-pipeline.ts status --build-id <BUILD_ID>


Alternatively, use the built-in `--watch` flag which handles polling automatically:

node .github/skills/azure-pipelines/azure-pipeline.ts queue

Use the build ID returned by the queue command

node .github/skills/azure-pipelines/azure-pipeline.ts status --build-id <BUILD_ID> --watch


**Note**: The `--watch` flag polls every 30 seconds by default. Use `--watch 60` for a 60-second interval to reduce API calls.

## Common Workflows

### 1. Quick Pipeline Validation

Make your YAML changes, then:

git add -A &#x26;&#x26; git commit -m "test: pipeline changes"

git push origin HEAD

Check for any previous builds on this branch and cancel if needed

node .github/skills/azure-pipelines/azure-pipeline.ts status

node .github/skills/azure-pipelines/azure-pipeline.ts cancel --build-id <id> # if there's an active build

Queue and watch the new build

node .github/skills/azure-pipelines/azure-pipeline.ts queue

node .github/skills/azure-pipelines/azure-pipeline.ts status --watch


### 2. Investigate a Build

Get overview of a build (shows stages, artifacts, and log IDs)

node .github/skills/azure-pipelines/azure-pipeline.ts status --build-id 123456

Download a specific log for deeper inspection

node .github/skills/azure-pipelines/azure-pipeline.ts status --build-id 123456 --download-log 5

Download an artifact

node .github/skills/azure-pipelines/azure-pipeline.ts status --build-id 123456 --download-artifact unsigned_vscode_cli_win32_x64_cli


### 3. Test with Modified Parameters

Customize build matrix for quicker validation

node .github/skills/azure-pipelines/azure-pipeline.ts queue \

--parameter "VSCODE_BUILD_TYPE=CI Build" \

--parameter "VSCODE_BUILD_WEB=false" \

--parameter "VSCODE_BUILD_ALPINE=false" \

--parameter "VSCODE_BUILD_ALPINE_ARM64=false" \

--parameter "VSCODE_PUBLISH=false"


### 4. Cancel a Running Build

First, find the build ID

node .github/skills/azure-pipelines/azure-pipeline.ts status

Cancel a specific build by ID

node .github/skills/azure-pipelines/azure-pipeline.ts cancel --build-id 123456

Dry run to see what would be cancelled

node .github/skills/azure-pipelines/azure-pipeline.ts cancel --build-id 123456 --dry-run


### 5. Iterate on Pipeline Changes

When iterating on pipeline YAML changes, always cancel obsolete builds before queueing new ones:

Push new changes

git add -A &#x26;&#x26; git commit --amend --no-edit

git push --force-with-lease origin HEAD

Find the outdated build ID and cancel it

node .github/skills/azure-pipelines/azure-pipeline.ts status

node .github/skills/azure-pipelines/azure-pipeline.ts cancel --build-id <id>

Queue a fresh build and monitor

node .github/skills/azure-pipelines/azure-pipeline.ts queue

node .github/skills/azure-pipelines/azure-pipeline.ts status --watch


## Troubleshooting

### Authentication Issues

Re-authenticate

az logout

az login

Check current account

az account show


### Extension Not Found

az extension add --name azure-devops --upgrade

BrowserAct

Let your agent run on any real-world website

Bypass CAPTCHA & anti-bot for free. Start local, scale to cloud.

Explore BrowserAct Skills →

Related skills

find-skills
2/3

Discover and install specialized agent skills from the open ecosystem when users need extended capabilities. Helps identify relevant skills by domain and task when users ask "how do I do X" or "find a skill for X" Integrates with the Skills CLI ( npx skills find , npx skills add ) to search, verify, and install packages from the skills.sh directory Recommends skills based on install count, source reputation, and GitHub stars to ensure quality before suggesting installation Presents skill options with install commands and links to skills.sh for user review and one-click installation

Verified authorvercel-labs
SKILLS.SH
1.5M19.6K
2026-05-22
vercel-react-best-practices
3/3

React and Next.js performance optimization guide with 64 prioritized rules across 8 categories. Organized by impact level, from critical waterfalls and bundle optimization down to advanced patterns, each rule includes incorrect/correct code examples and explanations Covers eight domains: async patterns, bundle size, server-side caching, client-side data fetching, re-render optimization, rendering performance, JavaScript efficiency, and advanced patterns Designed for use during component writing, code review, refactoring, and performance audits on React and Next.js applications Each rule has a prefix code (e.g., async-parallel , bundle-barrel-imports ) for easy reference in automated tooling and documentation

Verified authorvercel-labs
SKILLS.SH
389K26.9K
2026-05-22
azure-validate
2/3

Pre-deployment validation for Azure infrastructure, configuration, and permissions before deployment. Requires .azure/plan.md from a prior azure-prepare run; stops immediately if the plan is missing Executes recipe-specific validation commands (azd provision, bicep build, terraform validate) and records proof in the plan document Performs build verification, configuration checks, and permission validation; blocks deployment if any check fails Only authorized method to set plan status to Validated ; must be followed by azure-deploy skill to execute the actual deployment

Verified authormicrosoft
SKILLS.SH
324K1.1K
2026-05-22
appinsights-instrumentation
3/3

Guidance and reference material for instrumenting webapps with Azure Application Insights. Covers SDK setup, telemetry patterns, and configuration for ASP.NET Core and Node.js applications hosted in Azure Distinguishes between this skill (reference and guidance) and azure-prepare (actual implementation); invoke azure-prepare when the user wants to add instrumentation to their project Provides auto-instrumentation guidance for C# ASP.NET Core apps in Azure App Service, plus manual instrumentation paths for creating App Insights resources via Bicep templates or Azure CLI Includes language-specific code modification guides for ASP.NET Core, Node.js, and Python, plus quick references for OpenTelemetry SDKs and exporters

Verified authormicrosoft
SKILLS.SH
324K1.1K
2026-05-22

Stop writing automation&scrapers

Install the CLI. Run your first Skill in 30 seconds. Scale when you're ready.

Start free
free · no credit card