[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6999CQ2F922QHFEF16W45RR":3,"skill-same:01M6999CQ2F922QHFEF16W45RR":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6999CQ2F922QHFEF16W45RR","azure-pipelines",null,"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.","microsoft\u002Fvscode","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6998NK2WED5M549DX06VBCH",195270,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fazure-pipelines\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"azure","pipelines","azure pipelines","pipeline","when","changes","for","full","build","devops","use","ci","logs","yaml","code","status","azure devops","2026-11-10 10:12:30",false,"---\nname: azure-pipelines\ndescription: 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.\n---\n\n# Validating Azure Pipeline Changes\n\nWhen modifying Azure DevOps pipeline files (YAML files in `build\u002Fazure-pipelines\u002F`), 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.\n\n## Prerequisites\n\n1. **Check if Azure CLI is installed**:\n   ```bash\n   az --version\n   ```\n\n   If not installed, install it:\n   ```bash\n   # macOS\n   brew install azure-cli\n\n   # Windows (PowerShell as Administrator)\n   winget install Microsoft.AzureCLI\n\n   # Linux (Debian\u002FUbuntu)\n   curl -sL https:\u002F\u002Faka.ms\u002FInstallAzureCLIDeb | sudo bash\n   ```\n\n2. **Check if the DevOps extension is installed**:\n   ```bash\n   az extension show --name azure-devops\n   ```\n\n   If not installed, add it:\n   ```bash\n   az extension add --name azure-devops\n   ```\n\n3. **Authenticate**:\n   ```bash\n   az login\n   az devops configure --defaults organization=https:\u002F\u002Fdev.azure.com\u002Fmonacotools project=Monaco\n   ```\n\n## VS Code Main Build\n\nThe main VS Code build pipeline:\n- **Organization**: `monacotools`\n- **Project**: `Monaco`\n- **Definition ID**: `111`\n- **URL**: https:\u002F\u002Fdev.azure.com\u002Fmonacotools\u002FMonaco\u002F_build?definitionId=111\n\n## VS Code Insider Scheduled Builds\n\nTwo Insider builds run automatically on a scheduled basis:\n- **Morning build**: ~7:00 AM CET\n- **Evening build**: ~7:00 PM CET\n\nThese scheduled builds use the same pipeline definition (`111`) but run on the `main` branch to produce Insider releases.\n\n---\n\n## Queueing a Build\n\nUse the [queue command](.\u002Fazure-pipeline.ts) to queue a validation build:\n\n```bash\n# Queue a build on the current branch\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue\n\n# Queue with a specific source branch\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue --branch my-feature-branch\n\n# Queue with custom parameters\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue --parameter \"VSCODE_BUILD_WEB=false\" --parameter \"VSCODE_PUBLISH=false\"\n\n# Parameter value with spaces\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue --parameter \"VSCODE_BUILD_TYPE=Product Build\"\n```\n\n> **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:\n> ```bash\n> # Find the build ID from status, then cancel it\n> node .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status\n> node .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts cancel --build-id \u003Cid>\n> node .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue\n> ```\n\n### Script Options\n\n| Option | Description |\n|--------|-------------|\n| `--branch \u003Cname>` | Source branch to build (default: current git branch) |\n| `--definition \u003Cid>` | Pipeline definition ID (default: 111) |\n| `--parameter \u003Centry>` | Pipeline parameter in `KEY=value` format (repeatable); **use this when the value contains spaces** |\n| `--parameters \u003Clist>` | Space-separated parameters in `KEY=value KEY2=value2` format; values **must not** contain spaces |\n| `--dry-run` | Print the command without executing |\n\n### Product Build Queue Parameters (`build\u002Fazure-pipelines\u002Fproduct-build.yml`)\n\n| Name | Type | Default | Allowed Values | Description |\n|------|------|---------|----------------|-------------|\n| `VSCODE_QUALITY` | string | `insider` | `exploration`, `insider`, `stable` | Build quality channel |\n| `VSCODE_BUILD_TYPE` | string | `Product Build` | `Product`, `CI` | Build mode for Product vs CI |\n| `NPM_REGISTRY` | string | `https:\u002F\u002Fpkgs.dev.azure.com\u002Fmonacotools\u002FMonaco\u002F_packaging\u002Fvscode\u002Fnpm\u002Fregistry\u002F` | any URL | Custom npm registry |\n| `CARGO_REGISTRY` | string | `sparse+https:\u002F\u002Fpkgs.dev.azure.com\u002Fmonacotools\u002FMonaco\u002F_packaging\u002Fvscode\u002FCargo\u002Findex\u002F` | any URL | Custom Cargo registry |\n| `VSCODE_BUILD_WIN32` | boolean | `true` | `true`, `false` | Build Windows x64 |\n| `VSCODE_BUILD_WIN32_ARM64` | boolean | `true` | `true`, `false` | Build Windows arm64 |\n| `VSCODE_BUILD_LINUX` | boolean | `true` | `true`, `false` | Build Linux x64 |\n| `VSCODE_BUILD_LINUX_SNAP` | boolean | `true` | `true`, `false` | Build Linux x64 Snap |\n| `VSCODE_BUILD_LINUX_ARM64` | boolean | `true` | `true`, `false` | Build Linux arm64 |\n| `VSCODE_BUILD_LINUX_ARMHF` | boolean | `true` | `true`, `false` | Build Linux armhf |\n| `VSCODE_BUILD_ALPINE` | boolean | `true` | `true`, `false` | Build Alpine x64 |\n| `VSCODE_BUILD_ALPINE_ARM64` | boolean | `true` | `true`, `false` | Build Alpine arm64 |\n| `VSCODE_BUILD_MACOS` | boolean | `true` | `true`, `false` | Build macOS x64 |\n| `VSCODE_BUILD_MACOS_ARM64` | boolean | `true` | `true`, `false` | Build macOS arm64 |\n| `VSCODE_BUILD_MACOS_UNIVERSAL` | boolean | `true` | `true`, `false` | Build macOS universal (requires both macOS arches) |\n| `VSCODE_BUILD_WEB` | boolean | `true` | `true`, `false` | Build Web artifacts |\n| `VSCODE_PUBLISH` | boolean | `true` | `true`, `false` | Publish to builds.code.visualstudio.com |\n| `VSCODE_RELEASE` | boolean | `false` | `true`, `false` | Trigger release flow if successful |\n| `VSCODE_STEP_ON_IT` | boolean | `false` | `true`, `false` | Skip tests |\n| `VSCODE_USE_LEGACY_OSS_NOTICE` | boolean | `false` | `true`, `false` | Keep the legacy mixin ThirdPartyNotices.txt instead of the Component Governance notice |\n\nExample: run a quick CI-oriented validation with minimal publish\u002Frelease side effects:\n\n```bash\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue \\\n   --parameter \"VSCODE_BUILD_TYPE=CI Build\" \\\n   --parameter \"VSCODE_PUBLISH=false\" \\\n   --parameter \"VSCODE_RELEASE=false\"\n```\n\n---\n\n## Checking Build Status\n\nUse the [status command](.\u002Fazure-pipeline.ts) to monitor a running build:\n\n```bash\n# Get status of the most recent builds\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status\n\n# Get overview of a specific build by ID\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --build-id 123456\n\n# Watch build status (refreshes every 30 seconds)\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --watch\n\n# Watch with custom interval (60 seconds)\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --watch 60\n```\n\n### Script Options\n\n| Option | Description |\n|--------|-------------|\n| `--build-id \u003Cid>` | Specific build ID (default: most recent on current branch) |\n| `--branch \u003Cname>` | Filter builds by branch name (shows last 20 builds for branch) |\n| `--reason \u003Creason>` | Filter builds by reason: `manual`, `individualCI`, `batchedCI`, `schedule`, `pullRequest` |\n| `--definition \u003Cid>` | Pipeline definition ID (default: 111) |\n| `--watch [seconds]` | Continuously poll status until build completes (default: 30s) |\n| `--download-log \u003Cid>` | Download a specific log to \u002Ftmp |\n| `--download-artifact \u003Cname>` | Download artifact to \u002Ftmp |\n| `--json` | Output raw JSON for programmatic consumption |\n\n---\n\n## Cancelling a Build\n\nUse the [cancel command](.\u002Fazure-pipeline.ts) to stop a running build:\n\n```bash\n# Cancel a build by ID (use status command to find IDs)\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts cancel --build-id 123456\n\n# Dry run (show what would be cancelled)\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts cancel --build-id 123456 --dry-run\n```\n\n### Script Options\n\n| Option | Description |\n|--------|-------------|\n| `--build-id \u003Cid>` | Build ID to cancel (required) |\n| `--definition \u003Cid>` | Pipeline definition ID (default: 111) |\n| `--dry-run` | Print what would be cancelled without executing |\n\n---\n\n## Testing Pipeline Changes\n\nWhen the user asks to **test changes in an Azure Pipelines build**, follow this workflow:\n\n1. **Queue a new build** on the current branch\n2. **Poll for completion** by periodically checking the build status until it finishes\n\n### Polling for Build Completion\n\nUse a shell loop with `sleep` to poll the build status. The `sleep` command works on all major operating systems:\n\n```bash\n# Queue the build and note the build ID from output (e.g., 123456)\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue\n\n# Poll every 60 seconds until complete (works on macOS, Linux, and Windows with Git Bash\u002FWSL)\n# Replace \u003CBUILD_ID> with the actual build ID from the queue command\nwhile true; do\n  node .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --build-id \u003CBUILD_ID> --json 2>\u002Fdev\u002Fnull | grep -q '\"status\": \"completed\"' && break\n  sleep 60\ndone\n\n# Check final result\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --build-id \u003CBUILD_ID>\n```\n\nAlternatively, use the built-in `--watch` flag which handles polling automatically:\n\n```bash\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue\n# Use the build ID returned by the queue command\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --build-id \u003CBUILD_ID> --watch\n```\n\n> **Note**: The `--watch` flag polls every 30 seconds by default. Use `--watch 60` for a 60-second interval to reduce API calls.\n\n---\n\n## Common Workflows\n\n### 1. Quick Pipeline Validation\n\n```bash\n# Make your YAML changes, then:\ngit add -A && git commit -m \"test: pipeline changes\"\ngit push origin HEAD\n\n# Check for any previous builds on this branch and cancel if needed\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts cancel --build-id \u003Cid>  # if there's an active build\n\n# Queue and watch the new build\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --watch\n```\n\n### 2. Investigate a Build\n\n```bash\n# Get overview of a build (shows stages, artifacts, and log IDs)\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --build-id 123456\n\n# Download a specific log for deeper inspection\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --build-id 123456 --download-log 5\n\n# Download an artifact\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --build-id 123456 --download-artifact unsigned_vscode_cli_win32_x64_cli\n```\n\n### 3. Test with Modified Parameters\n\n```bash\n# Customize build matrix for quicker validation\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue \\\n   --parameter \"VSCODE_BUILD_TYPE=CI Build\" \\\n   --parameter \"VSCODE_BUILD_WEB=false\" \\\n   --parameter \"VSCODE_BUILD_ALPINE=false\" \\\n   --parameter \"VSCODE_BUILD_ALPINE_ARM64=false\" \\\n   --parameter \"VSCODE_PUBLISH=false\"\n```\n\n### 4. Cancel a Running Build\n\n```bash\n# First, find the build ID\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status\n\n# Cancel a specific build by ID\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts cancel --build-id 123456\n\n# Dry run to see what would be cancelled\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts cancel --build-id 123456 --dry-run\n```\n\n### 5. Iterate on Pipeline Changes\n\nWhen iterating on pipeline YAML changes, always cancel obsolete builds before queueing new ones:\n\n```bash\n# Push new changes\ngit add -A && git commit --amend --no-edit\ngit push --force-with-lease origin HEAD\n\n# Find the outdated build ID and cancel it\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts cancel --build-id \u003Cid>\n\n# Queue a fresh build and monitor\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --watch\n```\n\n---\n\n## Troubleshooting\n\n### Authentication Issues\n```bash\n# Re-authenticate\naz logout\naz login\n\n# Check current account\naz account show\n```\n\n### Extension Not Found\n```bash\naz extension add --name azure-devops --upgrade\n```\n\n### Rate Limiting\nIf you hit rate limits, add delays between API calls or use `--watch` with a longer interval.\n","# Validating Azure Pipeline Changes\n\nWhen modifying Azure DevOps pipeline files (YAML files in `build\u002Fazure-pipelines\u002F`), 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.\n\n## Prerequisites\n\n1. **Check if Azure CLI is installed**:\n   ```bash\n   az --version\n   ```\n\n   If not installed, install it:\n   ```bash\n   # macOS\n   brew install azure-cli\n\n   # Windows (PowerShell as Administrator)\n   winget install Microsoft.AzureCLI\n\n   # Linux (Debian\u002FUbuntu)\n   curl -sL https:\u002F\u002Faka.ms\u002FInstallAzureCLIDeb | sudo bash\n   ```\n\n2. **Check if the DevOps extension is installed**:\n   ```bash\n   az extension show --name azure-devops\n   ```\n\n   If not installed, add it:\n   ```bash\n   az extension add --name azure-devops\n   ```\n\n3. **Authenticate**:\n   ```bash\n   az login\n   az devops configure --defaults organization=https:\u002F\u002Fdev.azure.com\u002Fmonacotools project=Monaco\n   ```\n\n## VS Code Main Build\n\nThe main VS Code build pipeline:\n- **Organization**: `monacotools`\n- **Project**: `Monaco`\n- **Definition ID**: `111`\n- **URL**: https:\u002F\u002Fdev.azure.com\u002Fmonacotools\u002FMonaco\u002F_build?definitionId=111\n\n## VS Code Insider Scheduled Builds\n\nTwo Insider builds run automatically on a scheduled basis:\n- **Morning build**: ~7:00 AM CET\n- **Evening build**: ~7:00 PM CET\n\nThese scheduled builds use the same pipeline definition (`111`) but run on the `main` branch to produce Insider releases.\n\n---\n\n## Queueing a Build\n\nUse the [queue command](.\u002Fazure-pipeline.ts) to queue a validation build:\n\n```bash\n# Queue a build on the current branch\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue\n\n# Queue with a specific source branch\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue --branch my-feature-branch\n\n# Queue with custom parameters\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue --parameter \"VSCODE_BUILD_WEB=false\" --parameter \"VSCODE_PUBLISH=false\"\n\n# Parameter value with spaces\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue --parameter \"VSCODE_BUILD_TYPE=Product Build\"\n```\n\n> **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:\n> ```bash\n> # Find the build ID from status, then cancel it\n> node .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status\n> node .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts cancel --build-id \u003Cid>\n> node .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue\n> ```\n\n### Script Options\n\n| Option | Description |\n|--------|-------------|\n| `--branch \u003Cname>` | Source branch to build (default: current git branch) |\n| `--definition \u003Cid>` | Pipeline definition ID (default: 111) |\n| `--parameter \u003Centry>` | Pipeline parameter in `KEY=value` format (repeatable); **use this when the value contains spaces** |\n| `--parameters \u003Clist>` | Space-separated parameters in `KEY=value KEY2=value2` format; values **must not** contain spaces |\n| `--dry-run` | Print the command without executing |\n\n### Product Build Queue Parameters (`build\u002Fazure-pipelines\u002Fproduct-build.yml`)\n\n| Name | Type | Default | Allowed Values | Description |\n|------|------|---------|----------------|-------------|\n| `VSCODE_QUALITY` | string | `insider` | `exploration`, `insider`, `stable` | Build quality channel |\n| `VSCODE_BUILD_TYPE` | string | `Product Build` | `Product`, `CI` | Build mode for Product vs CI |\n| `NPM_REGISTRY` | string | `https:\u002F\u002Fpkgs.dev.azure.com\u002Fmonacotools\u002FMonaco\u002F_packaging\u002Fvscode\u002Fnpm\u002Fregistry\u002F` | any URL | Custom npm registry |\n| `CARGO_REGISTRY` | string | `sparse+https:\u002F\u002Fpkgs.dev.azure.com\u002Fmonacotools\u002FMonaco\u002F_packaging\u002Fvscode\u002FCargo\u002Findex\u002F` | any URL | Custom Cargo registry |\n| `VSCODE_BUILD_WIN32` | boolean | `true` | `true`, `false` | Build Windows x64 |\n| `VSCODE_BUILD_WIN32_ARM64` | boolean | `true` | `true`, `false` | Build Windows arm64 |\n| `VSCODE_BUILD_LINUX` | boolean | `true` | `true`, `false` | Build Linux x64 |\n| `VSCODE_BUILD_LINUX_SNAP` | boolean | `true` | `true`, `false` | Build Linux x64 Snap |\n| `VSCODE_BUILD_LINUX_ARM64` | boolean | `true` | `true`, `false` | Build Linux arm64 |\n| `VSCODE_BUILD_LINUX_ARMHF` | boolean | `true` | `true`, `false` | Build Linux armhf |\n| `VSCODE_BUILD_ALPINE` | boolean | `true` | `true`, `false` | Build Alpine x64 |\n| `VSCODE_BUILD_ALPINE_ARM64` | boolean | `true` | `true`, `false` | Build Alpine arm64 |\n| `VSCODE_BUILD_MACOS` | boolean | `true` | `true`, `false` | Build macOS x64 |\n| `VSCODE_BUILD_MACOS_ARM64` | boolean | `true` | `true`, `false` | Build macOS arm64 |\n| `VSCODE_BUILD_MACOS_UNIVERSAL` | boolean | `true` | `true`, `false` | Build macOS universal (requires both macOS arches) |\n| `VSCODE_BUILD_WEB` | boolean | `true` | `true`, `false` | Build Web artifacts |\n| `VSCODE_PUBLISH` | boolean | `true` | `true`, `false` | Publish to builds.code.visualstudio.com |\n| `VSCODE_RELEASE` | boolean | `false` | `true`, `false` | Trigger release flow if successful |\n| `VSCODE_STEP_ON_IT` | boolean | `false` | `true`, `false` | Skip tests |\n| `VSCODE_USE_LEGACY_OSS_NOTICE` | boolean | `false` | `true`, `false` | Keep the legacy mixin ThirdPartyNotices.txt instead of the Component Governance notice |\n\nExample: run a quick CI-oriented validation with minimal publish\u002Frelease side effects:\n\n```bash\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue \\\n   --parameter \"VSCODE_BUILD_TYPE=CI Build\" \\\n   --parameter \"VSCODE_PUBLISH=false\" \\\n   --parameter \"VSCODE_RELEASE=false\"\n```\n\n---\n\n## Checking Build Status\n\nUse the [status command](.\u002Fazure-pipeline.ts) to monitor a running build:\n\n```bash\n# Get status of the most recent builds\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status\n\n# Get overview of a specific build by ID\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --build-id 123456\n\n# Watch build status (refreshes every 30 seconds)\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --watch\n\n# Watch with custom interval (60 seconds)\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --watch 60\n```\n\n### Script Options\n\n| Option | Description |\n|--------|-------------|\n| `--build-id \u003Cid>` | Specific build ID (default: most recent on current branch) |\n| `--branch \u003Cname>` | Filter builds by branch name (shows last 20 builds for branch) |\n| `--reason \u003Creason>` | Filter builds by reason: `manual`, `individualCI`, `batchedCI`, `schedule`, `pullRequest` |\n| `--definition \u003Cid>` | Pipeline definition ID (default: 111) |\n| `--watch [seconds]` | Continuously poll status until build completes (default: 30s) |\n| `--download-log \u003Cid>` | Download a specific log to \u002Ftmp |\n| `--download-artifact \u003Cname>` | Download artifact to \u002Ftmp |\n| `--json` | Output raw JSON for programmatic consumption |\n\n---\n\n## Cancelling a Build\n\nUse the [cancel command](.\u002Fazure-pipeline.ts) to stop a running build:\n\n```bash\n# Cancel a build by ID (use status command to find IDs)\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts cancel --build-id 123456\n\n# Dry run (show what would be cancelled)\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts cancel --build-id 123456 --dry-run\n```\n\n### Script Options\n\n| Option | Description |\n|--------|-------------|\n| `--build-id \u003Cid>` | Build ID to cancel (required) |\n| `--definition \u003Cid>` | Pipeline definition ID (default: 111) |\n| `--dry-run` | Print what would be cancelled without executing |\n\n---\n\n## Testing Pipeline Changes\n\nWhen the user asks to **test changes in an Azure Pipelines build**, follow this workflow:\n\n1. **Queue a new build** on the current branch\n2. **Poll for completion** by periodically checking the build status until it finishes\n\n### Polling for Build Completion\n\nUse a shell loop with `sleep` to poll the build status. The `sleep` command works on all major operating systems:\n\n```bash\n# Queue the build and note the build ID from output (e.g., 123456)\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue\n\n# Poll every 60 seconds until complete (works on macOS, Linux, and Windows with Git Bash\u002FWSL)\n# Replace \u003CBUILD_ID> with the actual build ID from the queue command\nwhile true; do\n  node .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --build-id \u003CBUILD_ID> --json 2>\u002Fdev\u002Fnull | grep -q '\"status\": \"completed\"' && break\n  sleep 60\ndone\n\n# Check final result\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --build-id \u003CBUILD_ID>\n```\n\nAlternatively, use the built-in `--watch` flag which handles polling automatically:\n\n```bash\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue\n# Use the build ID returned by the queue command\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --build-id \u003CBUILD_ID> --watch\n```\n\n> **Note**: The `--watch` flag polls every 30 seconds by default. Use `--watch 60` for a 60-second interval to reduce API calls.\n\n---\n\n## Common Workflows\n\n### 1. Quick Pipeline Validation\n\n```bash\n# Make your YAML changes, then:\ngit add -A && git commit -m \"test: pipeline changes\"\ngit push origin HEAD\n\n# Check for any previous builds on this branch and cancel if needed\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts cancel --build-id \u003Cid>  # if there's an active build\n\n# Queue and watch the new build\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --watch\n```\n\n### 2. Investigate a Build\n\n```bash\n# Get overview of a build (shows stages, artifacts, and log IDs)\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --build-id 123456\n\n# Download a specific log for deeper inspection\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --build-id 123456 --download-log 5\n\n# Download an artifact\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --build-id 123456 --download-artifact unsigned_vscode_cli_win32_x64_cli\n```\n\n### 3. Test with Modified Parameters\n\n```bash\n# Customize build matrix for quicker validation\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue \\\n   --parameter \"VSCODE_BUILD_TYPE=CI Build\" \\\n   --parameter \"VSCODE_BUILD_WEB=false\" \\\n   --parameter \"VSCODE_BUILD_ALPINE=false\" \\\n   --parameter \"VSCODE_BUILD_ALPINE_ARM64=false\" \\\n   --parameter \"VSCODE_PUBLISH=false\"\n```\n\n### 4. Cancel a Running Build\n\n```bash\n# First, find the build ID\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status\n\n# Cancel a specific build by ID\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts cancel --build-id 123456\n\n# Dry run to see what would be cancelled\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts cancel --build-id 123456 --dry-run\n```\n\n### 5. Iterate on Pipeline Changes\n\nWhen iterating on pipeline YAML changes, always cancel obsolete builds before queueing new ones:\n\n```bash\n# Push new changes\ngit add -A && git commit --amend --no-edit\ngit push --force-with-lease origin HEAD\n\n# Find the outdated build ID and cancel it\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts cancel --build-id \u003Cid>\n\n# Queue a fresh build and monitor\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts queue\nnode .github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts status --watch\n```\n\n---\n\n## Troubleshooting\n\n### Authentication Issues\n```bash\n# Re-authenticate\naz logout\naz login\n\n# Check current account\naz account show\n```\n\n### Extension Not Found\n```bash\naz extension add --name azure-devops --upgrade\n```\n\n### Rate Limiting\nIf you hit rate limits, add delays between API calls or use `--watch` with a longer interval.\n",{"name":5,"description":7},"main","11ba54a90a0ff8720cf47c086f5a9948eef9cf2c",".github\u002Fskills\u002Fazure-pipelines",43791,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode","https:\u002F\u002Fcode.visualstudio.com","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 03:13:10",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add microsoft\u002Fvscode --skill azure-pipelines",{"tool":62,"command":63},"bunx","bunx skills add microsoft\u002Fvscode --skill azure-pipelines",{"tool":65,"command":66},"pnpm","pnpm dlx skills add microsoft\u002Fvscode --skill azure-pipelines","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fazure-pipelines\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"azure-pipeline.ts","SCRIPT","脚本",63771,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fazure-pipelines\u002Fazure-pipeline.ts",[77,102,123,136,151,167],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":41},"01M70H0ANBKZAVEP1NVV4K28M3","sweeper-query","Answer natural-language questions about the VS Code Sweeper's published issue index (index-\u003Cname>.json for microsoft\u002Fvscode and the enrolled family repos) — which issues are agent-ready to implement or plan, what the sweeper proposed for an assignee or area, whether the sweeper knows a report as a duplicate, the highest-value open bugs in a lane — and, for one issue, the review's full record (evidence with file citations, fix brief, proposed comment). Use ONLY when the request explicitly names the sweeper — \"sweeper\", \"vscodesweeper\", \"sweeper-query\", a sweeper verdict, record, brief or index, an agent-ready issue — or asks what \"the sweeper\" found, proposed or knows. Do NOT use for general questions about issues, duplicates, priorities or ranking that do not mention the sweeper. Read-only; discovery only.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsweeper-query\u002FSKILL.md",[],[84,85,86,87,88,28,89,90,91,92,93,94,95,96,97,98,99,100,101,38],"sweeper query","query","sweeper","review","fix","request","which","natural-language","ranking","duplicates","ready","only","read","plan","open","Citations","brief","issues",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":41},"01M699DRJS4YJCV600Q72SVVWE","update-skills","Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says \"learn!\", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fupdate-skills\u002FSKILL.md",[],[109,110,30,111,112,113,114,34,115,116,117,118,119,120,121,122,28],"update","update skills","pattern","domain","learnings","reusable","session","user","instructions","knowledge","repository","learn","create","sessions",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":41},"01M699DPWHZ72B66P82EW31RNE","update-pr","Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fupdate-pr\u002FSKILL.md",[],[109,130,131,28,89,132,30,34,115,116,133,134,135,29],"pr","update pr","Existing","push","pull","pull request",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":41},"01M699DJMR6CE1MH5XCJZ0GFQ0","sync","Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fsync\u002FSKILL.md",[],[138,143,144,133,134,145,28,29,146,147,148,149,34,115,116,150],"SET","publish","rebase","latest","with","remote","upstream","branch",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":41},"01M699DGXHX6A2A72X57R6GGHJ","sync-upstream","Update a stale session branch by rebasing onto the latest origin. Use when the upstream has moved significantly and the session needs to catch up, resolving conflicts by preserving upstream changes and adapting session work to fit.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fsync-upstream\u002FSKILL.md",[],[149,138,158,159,28,160,161,29,146,162,163,164,165,34,115,150,166,109],"sync upstream","fit","catch","catch up","origin","conflicts","stale","up","work",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":41},"01M699DEXYFWDGW0BAXJ5QQ377","merge","Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode\u002Fblob\u002Fmain\u002Fsrc\u002Fvs\u002Fsessions\u002Fskills\u002Fmerge\u002FSKILL.md",[],[169,115,34,166,150,116,28,174,175,29],"back","base"]