Azure DevOps Pipeline Notifier
Get instant notifications in VS Code when you run Azure DevOps pipelines and when they complete!
Features
- 🚀 Start Notifications: Get notified immediately when a pipeline you triggered starts running
- ✅ Completion Notifications: Receive alerts when pipelines finish with their result status
- 🔗 Quick Access: Click notifications to open pipeline results directly in Azure DevOps
- ⚙️ Auto-start: Automatically start monitoring when VS Code launches
- 🎯 Personal Tracking: Only tracks pipelines you manually triggered
Notification Examples
Pipeline Start:
🚀 Pipeline Started: Build-Deploy (Build [#123](https://github.com/AlfazSadoolah/pipeline-notifier/issues/123))
[View Pipeline] [Dismiss]
Pipeline Success:
✅ Pipeline Succeeded: Build-Deploy (Build [#123](https://github.com/AlfazSadoolah/pipeline-notifier/issues/123))
[View Results] [Dismiss]
Pipeline Failure:
❌ Pipeline Failed: Build-Deploy (Build [#123](https://github.com/AlfazSadoolah/pipeline-notifier/issues/123))
[View Logs] [Dismiss]
Setup
1. Install the Extension
Install this extension from the VS Code marketplace or VSIX file.
Open VS Code Settings (Ctrl+, or Cmd+,) and search for "Pipeline Notifier":
- ADO Organization URL: Your Azure DevOps organization (e.g.,
https://dev.azure.com/yourorg)
- ADO Project Name: Your project name
- ADO User Email: Your Azure DevOps email address
- ADO Personal Access Token (PAT): Your PAT with Build (Read) permissions
3. Create a Personal Access Token
- Go to Azure DevOps → User Settings → Personal Access Tokens
- Click "New Token"
- Set name (e.g., "VS Code Pipeline Notifier")
- Select scopes:
- Copy the token and paste it in VS Code settings
Usage
Manual Control
Use the Command Palette (Ctrl+Shift+P or Cmd+Shift+P):
Start Azure DevOps Pipeline Monitoring - Begin monitoringStop Azure DevOps Pipeline Monitoring - Stop monitoring
Auto-start
By default, monitoring starts automatically when VS Code launches. Disable this in settings if you prefer manual control.
Configuration
| Setting |
Description |
Default |
pipelineNotifier.adoOrg |
Azure DevOps Organization URL |
- |
pipelineNotifier.adoProject |
Project name |
- |
pipelineNotifier.adoUserEmail |
Your email address |
- |
pipelineNotifier.adoPat |
Personal Access Token |
- |
pipelineNotifier.pollingInterval |
Check interval in milliseconds |
5000 |
pipelineNotifier.autoStart |
Auto-start on launch |
true |
How It Works
- Polling: Checks Azure DevOps Build API every 5 seconds (configurable)
- User Filtering: Only tracks pipeline runs you triggered manually
- State Tracking: Monitors pipeline state transitions (notStarted → inProgress → completed)
- Dual Notifications: Sends one notification when started, another when completed
- Smart Cleanup: Automatically cleans up completed runs after 24 hours
Result Types
- ✅ Succeeded: All tasks passed
- ❌ Failed: One or more tasks failed
- ⚠️ Partially Succeeded: Some tasks passed with warnings
- 🚫 Canceled: Pipeline was canceled
Troubleshooting
No notifications appearing?
- Verify your Azure DevOps credentials are correct
- Check that your PAT has Build (Read) permissions
- Ensure you're triggering pipelines manually (not via CI/CD triggers)
- Check VS Code Developer Tools console for errors (
Help → Toggle Developer Tools)
Too many/few notifications?
Adjust the pipelineNotifier.pollingInterval setting:
- Faster: 5000 (5 seconds)
- Slower: 15000 (15 seconds) or 30000 (30 seconds)
Privacy & Security
- Your PAT is stored in VS Code's secure settings
- All API calls go directly to Azure DevOps (no third-party servers)
- Only tracks your own pipeline runs
License
MIT License - see LICENSE file for details
Credits
Built with inspiration from the ADO Tasks Notifier extension.
Support
Found a bug or have a feature request? Open an issue on GitHub!
