Many of our customers use Slack channels to manage Azure Pipelines. Today, we’re making it even easier for you, with a tighter integration that lets you be more productive – even when you’re on the go!
Going forward approving release deployments in Azure Pipelines is just a click away. Once you subscribe to ‘Release deployment approval pending’ notification in Slack (which happens by default upon subscribing to any release pipeline), you can approve/reject deployments by clicking on the notification. What’s more, it supports all the approval scenarios in Azure Pipelines portal.
You can try the Azure Pipelines app for Slack by installing it with one click. Check out our documentation for more information!
We have been getting a lot of quality feedback which have been of great help in shaping our direction. We would love to hear from you about this app and its features. Please provide your feedback here.
Can we do a pre approval at a Task level . Let me explain . Consider i have a Task Terraform which awaits plan approval , can we get the confirmation integrated through Slack . If it is already not available in case .
The app supports the same capabilities as the website. I believe the portal does not allow approvals at task level, only at stage level and hence that is what the app supports today. Thanks!
Will this work with on-prem Azure Devops? When I tried to “log in”, I get taken to a VSTS page to log in vs. on-prem (even after using /azpipelins subscribe <publicly available URL for on-prem TFS>)
Hi Craig, this is currently only available for Azure DevOps (hosted) and not for Azure DevOps Server (onprem). Thanks!
Would love this in Teams!
This functionality is now available in the Azure Pipelines app for Teams: https://appsource.microsoft.com/en-us/product/office/WA200000055 or just search for Azure Pipelines in the Teams apps marketplace. Thanks!
Same here!!
Remember me when I owned a Windows Phone, all other platform stores receive Microsoft apps first then Windows mobile store. However, I’m looking forward to it too.
Thanks for your interest @George. This functionality will be coming to Teams soon.