What’s new in Azure DevOps Sprint 161
Sprint 161 has just finished rolling out to all organizations and you can check out all the new features in the release notes. Here are some of the features that you can start using today.
Create bulk subscriptions in Azure Pipelines app for Slack and Microsoft Teams
Users of the Azure Pipelines app for Slack and Microsoft Teams can now bulk subscribe to all of the pipelines in a project. You can use filters to manage what gets posted in the Slack or Teams channels. You can continue to subscribe to individual pipelines too.
Checkout multiple repositories in Azure Pipelines
Pipelines often rely on multiple repositories. You can have different repositories with source, tools, scripts, or other items that you need to build your code. Previously, you had to add these repositories as submodules or as manual scripts to run git checkout. Now you can fetch and check out other repositories, in addition to the one you use to store your YAML pipeline.
Use GitHub Actions to trigger a run in Azure Pipelines
GitHub Actions make it easy to build, test, and deploy your code right from GitHub. We now have GitHub Actions for Azure Pipelines (Azure/pipelines). You can use Azure/pipelines to trigger a run in Azure Pipelines as part of your GitHub Actions workflow.
You can use this action to trigger a specific pipeline (YAML or classic release pipeline) in Azure DevOps. GitHub Actions will take the Project URL, pipeline name, and a Personal Access Token (PAT) for your Azure DevOps organization as inputs.
These are just the tip of the iceberg, and there are plenty more features that we’ve released in Sprint 161. Check out the full list of features for this sprint in the release notes.
Multiple checkout is really cool feature, where it was one year ago, when I built a pipeline for a big team:) would be great if azure could be check that repository was not changed and can’t build project again, I know that it’s not simple,but would be great) thanks for your work!
Wouldn’t you be able to use path filters for that?
Oh, so that’s why build tag filtering suddenly stopped working. Multi-repo is a welcomed addition though.
Is this only available in yaml pipelines? What about the classic ones? We are still actively using the classical pipeline for much of our pipelines as not all features are available in yaml pipeline. One being the task group.
Will you do a post on whats new in Sprint 162?..I’m waiting to highlight the lack of notifications for the new ‘service connection approval/check feature’ a problem which also exists for environment check/approvals.
Multistage Pipelines would be so great if it just allowed some form of notifications to go out when stuff needs approval.