You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/wwl-data-ai/implement-cicd-in-fabric/includes/4-implement-deployment-pipelines.md
+7-10Lines changed: 7 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
Pipelines enable a continuous integration/continuous deployment (CI/CD) approach that ensures content is updated, tested, and regularly refreshed. Pipelines are an efficient and durable way to automate the movement of content through the development, test, and production stages of the content development lifecycle.
1
+
Pipelines enable a continuous integration/continuous deployment (CI/CD) approach that ensures content is updated, tested, and regularly refreshed. Pipelines are a way to automate the movement of content through the development, test, and production stages of the content development lifecycle.
2
2
3
-
## What is deployment pipelines
3
+
## What are Fabric deployment pipelines
4
4
5
5
Fabric deployment pipelines help you deploy your Fabric items across different environments like development, test, and production. They let you develop and test content in Fabric before it reaches end users.
6
6
@@ -14,20 +14,17 @@ Follow these steps to create a deployment pipeline:
14
14
1. Select the **Workspaces** icon on the left navigation pane, then **Deployment pipelines.**
15
15
16
16
2. Select **New pipeline**. Then name the pipeline and select **Next**.
17
-
3. Define, and name the stages in your pipeline. Then select **Create.**
17
+
3. Define, and name the stages in your pipeline. Then select **Create and continue.**
18
18
19
19
:::image type="content" source="../media/create-stages.png" alt-text="Screenshot of pipeline stage selector." :::
20
-
4. Assign a workspace to a stage.
20
+
4. Assign a workspace to a stage. Then select the green check mark next to the stage. Then you're ready to deploy content to the pipeline.
21
21
22
22
:::image type="content" source="../media/assign-workspace.png" alt-text="Screenshot of workspace assignment interface." :::
23
-
5. Now you're ready to deploy content to the pipeline.
24
-
25
-
:::image type="content" source="../media/pipeline-setup.png" alt-text="Screenshot of pipeline without content." :::
26
23
27
24
## Deploy content to a pipeline stage
28
25
The deployment process lets you clone content from one stage in the pipeline to another, typically from development to test, and from test to production.
29
26
30
-
To deploy content between stages, select the stage to deploy from, and then select the **Deploy** button. The deployment process copies all of the workspace content into the target stage. In the following image, there's a data pipeline that only exists in the development stage that will be moved to the test stage when **Deploy** is selected in the development stage.
27
+
To deploy content between stages, select the stage to deploy to, and then select the stage in the **Deploy from** drop down box, and then select the **Deploy** button. The deployment process copies all of the workspace content into the target stage. In the following image, there's a data pipeline that only exists in the development stage that will be moved to the test stage when **Deploy** is selected in the development stage.
31
28
32
29
:::image type="content" source="../media/deploy-content.png" alt-text="Screenshot of content deployment interface." :::
33
30
@@ -40,9 +37,9 @@ To use deployment pipelines with Git branches:
40
37
41
38
:::image type="content" source="../media/connect-git.png" alt-text="Screenshot of workspace to Git provider connection interface." :::
42
39
43
-
3. Promote content between staging environments using the deploy button in the pipeline as described in the **Deploy content to a pipeline stage** section on this page. This moves content between environments in Fabric but the Git repository won't be updated until you manually update from the workspace.
40
+
3. Promote content between staging environments using the deploy button in the pipeline as described in the **Deploy content to a pipeline stage** section on this page. This moves content between environments in Fabric but *the Git repository won't be updated until you manually update from the workspace.*
44
41
45
-
In the image below, we see that a data pipeline item exists in all three staging environments of the deployment pipeline *in Fabric* and that the Fabric stages are synchronized.
42
+
In the image below, the checkmark in the deployment stage box indicates that a data pipeline item exists in all three staging environments of the deployment pipeline *in Fabric* and that the Fabric stages are synchronized.
46
43
47
44
:::image type="content" source="../media/pipeline-presync.png" alt-text="Screenshot of pipeline before files are synced with Git." :::
0 commit comments