Introduction to deployment pipelines
In today’s world, analytics is a vital part of decision making in almost every organization. The growing use of Power BI as an analytics tool, requires it to use more data, look appealing and be user-friendly. Above all however, Power BI needs to always be available and reliable. To meet these requirements, BI creators must collaborate effectively.
The deployment pipelines tool enables BI creators to manage the lifecycle of organizational content. It's an efficient and reusable tool for creators in an enterprise with Premium capacity. Deployment pipelines enable creators to develop and test Power BI content in the Power BI service, before the content is consumed by users. The content types include reports, paginated reports, dashboards, datasets and dataflows.
Learn to use deployment pipelines
You can learn how to use the deployment pipelines tool by following these links.
Create and manage a Power BI deployment pipeline - A Power BI Learn module that walks you through creating a deployment pipeline.
Get started with deployment pipelines - A Power BI article that explains how to create a pipeline, as well as key functions such as backward deployment and deployment rules.
Deployment pipelines is designed as a pipeline with three stages:
This stage is used to design, build, and upload new content with fellow creators. This is the first stage in deployment pipelines.
You're ready to enter the test stage after you've made all the needed changes to your content. You upload the modified content so it can be moved to this test stage. Here are three examples of what can be done in the test environment:
Share content with testers and reviewers
Load and run tests with larger volumes of data
Test your app to see how it will look for your end users
After testing the content, use the production stage to share the final version of your content with business users across the organization.
When you deploy content from the source stage to a target stage, the source content will overwrite anything with the same name in the target stage. Content in the target stage that doesn't exist in the source stage remains in the target stage as is. After you select deploy, you'll get a warning message listing the items that will be overwritten.