Happy new year everyone!
Since 2022 has started, we have released new deployment pipelines features, that enable plenty of new ways to work with deployment pipelines and leverage its advantages for a more productive release process.
Power BI automation tools extension for Azure DevOps Deployment_pipelines-_Azure_DevOps_extension_multiple_pipelines_working_together
During October, we announced that deployment pipelines REST APIs are generally available. Now we are releasing the first official Power BI extension for the Visual Studio marketplace- Power BI automation tools.Deployment_pipelines-_Azure_DevOps_extension_multiple_pipelines_working_together
Using the extension, it will be easier than ever to automate your deployment operations using Azure pipelines.
The extension contains all the API operations available today for deployment pipelines. Using the extension, you can set tasks for:
- Creating and editing pipelines
- Assigning workspaces
- Adding users to a pipeline and a workspace
- Managing deployments across the pipeline stages
Learn more about the Power BI automation tools extension.
Multiple pipelines working together
One of the biggest advantages of deployment pipelines, is auto-binding. With auto-binding, you don’t need to worry about how items will connect across different stages or configure all these connections every time. Deployment pipelines just does it for you, and that reduces manual work and errors.Today we are very happy to unlock this capability across multiple pipelines. For example, if you have datasets managed in one pipeline, and connected reports are managed in other pipelines by different groups, the auto binding will work in the same way it works in a single pipeline. We will auto-bind connections between the same stages, even in separate pipelines.
Deployment_pipelines-_Azure_DevOps_extension_multiple_pipelines_working_together
How can you enable it?
Well… you don’t have to do anything! It will just work starting as of now. All you need to do is make sure that items are connected across the same stages. For example, if a dataset in the development stage is connected to a report in the development stage of another pipeline, when both will be deployed to the test stage, they will be automatically connected to each other.
Learn more about multiple pipelines working together.