azure-pipelineslisted

# 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: ```bash # macOS brew install azure-cli # Windows (PowerShell as Administrator) winget install Microsoft.AzureCLI # Linux (Debian/Ubuntu) curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash ``` 2. **Check if the DevOps extension is installed**: ```bash az extension show --name azure-devops ``` If not installed, add it: ```bash az extension add --name azure-devops ``` 3. **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. --- ## Qu