Skip to content

Commit de7e24b

Browse files
v-dirichardsv-dirichards
authored
Merge pull request #47886 from MicrosoftDocs/release-fabric-cicd
Release fabric cicd
2 parents 146697c + bd62e30 commit de7e24b

28 files changed

+362
-0
lines changed

‎learn-pr/wwl-data-ai/implement-cicd-in-fabric/1-introduction.yml

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn-wwl.implement-cicd-in-fabric.introduction
3+
title: Introduction
4+
metadata:
5+
title: Introduction
6+
description: "Introduction"
7+
ms.date: 11/8/2024
8+
author: wwlpublish
9+
ms.author: theresai
10+
ms.topic: unit
11+
durationInMinutes: 3
12+
content: |
13+
[!include[](includes/1-introduction.md)]

‎learn-pr/wwl-data-ai/implement-cicd-in-fabric/2-understand-cicd.yml

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn-wwl.implement-cicd-in-fabric.understand-cicd
3+
title: Understand Continuous Integration and Continuous Delivery (CI/CD)
4+
metadata:
5+
title: Understand Continuous Integration and Continuous Delivery (CI/CD)
6+
description: "Learn about Continuous Integration and Continuous Delivery (CI/CD) and how to use it in Fabric."
7+
ms.date: 11/8/2024
8+
author: wwlpublish
9+
ms.author: theresai
10+
ms.topic: unit
11+
durationInMinutes: 5
12+
content: |
13+
[!include[](includes/2-understand-cicd.md)]

‎learn-pr/wwl-data-ai/implement-cicd-in-fabric/3-implement-version-control-and-git-integration.yml

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn-wwl.implement-cicd-in-fabric.implement-version-control-and-git-integration
3+
title: Implement version control and Git integration
4+
metadata:
5+
title: Implement version control and Git integration
6+
description: "Learn how to implement version control and Git integration in Microsoft Fabric."
7+
ms.date: 11/8/2024
8+
author: wwlpublish
9+
ms.author: theresai
10+
ms.topic: unit
11+
durationInMinutes: 6
12+
content: |
13+
[!include[](includes/3-implement-version-control-and-git-integration.md)]

‎learn-pr/wwl-data-ai/implement-cicd-in-fabric/4-implement-deployment-pipelines.yml

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn-wwl.implement-cicd-in-fabric.implement-deployment-pipelines
3+
title: Implement deployment pipelines
4+
metadata:
5+
title: Implement deployment pipelines
6+
description: "Learn how to implement deployment pipelines in Microsoft Fabric."
7+
ms.date: 11/8/2024
8+
author: wwlpublish
9+
ms.author: theresai
10+
ms.topic: unit
11+
durationInMinutes: 6
12+
content: |
13+
[!include[](includes/4-implement-deployment-pipelines.md)]

‎learn-pr/wwl-data-ai/implement-cicd-in-fabric/5-automate-cicd-using-fabric-apis.yml

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn-wwl.implement-cicd-in-fabric.automate-cicd-using-fabric-apis
3+
title: Automate CI/CD using Fabric APIs
4+
metadata:
5+
title: Automate CI/CD using Fabric APIs
6+
description: "Learn how to automate CI/CD using Fabric APIs."
7+
ms.date: 11/8/2024
8+
author: wwlpublish
9+
ms.author: theresai
10+
ms.topic: unit
11+
durationInMinutes: 2
12+
content: |
13+
[!include[](includes/5-automate-cicd-using-fabric-apis.md)]

‎learn-pr/wwl-data-ai/implement-cicd-in-fabric/6-exercise-implement-deployment-pipelines.yml

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn-wwl.implement-cicd-in-fabric.exercise
3+
title: 'Exercise: Implement deployment pipelines in Microsoft Fabric'
4+
metadata:
5+
title: 'Exercise: Implement deployment pipelines in Microsoft Fabric'
6+
description: "Learn how to implement deployment pipelines in Microsoft Fabric."
7+
ms.date: 11/8/2024
8+
author: wwlpublish
9+
ms.author: theresai
10+
ms.topic: unit
11+
durationInMinutes: 20
12+
content: |
13+
[!include[](includes/6-exercise-implement-deployment-pipelines.md)]

‎learn-pr/wwl-data-ai/implement-cicd-in-fabric/7-knowledge-check.yml

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn-wwl.implement-cicd-in-fabric.knowledge-check
3+
title: Knowledge check
4+
metadata:
5+
title: Knowledge check
6+
description: "Knowledge check"
7+
ms.date: 11/8/2024
8+
author: wwlpublish
9+
ms.author: theresai
10+
ms.topic: unit
11+
durationInMinutes: 3
12+
quiz:
13+
questions:
14+
- content: What is the role of Git in the CI/CD process in Fabric?
15+
choices:
16+
- content: Git is used to deploy code changes to different environments.
17+
isCorrect: false
18+
explanation: Incorrect. Git isn't used for deployment. It's used for version control and collaboration.
19+
- content: Git is used for automated testing of code changes.
20+
isCorrect: false
21+
explanation: Incorrect. Git doesn't perform automated testing, it's used for version control and collaboration.
22+
- content: Git lets your team collaborate using branches, and provides version control. It helps manage incremental code changes, and see code history.
23+
isCorrect: true
24+
explanation: Correct. Git is used for version control and collaboration, allowing teams to manage code changes and view code history.
25+
26+
27+
- content: What is the purpose of connecting a Fabric workspace to a Git repository?
28+
choices:
29+
- content: To automatically deploy changes made in the workspace to a live environment.
30+
isCorrect: false
31+
explanation: Incorrect. The connection of a Fabric workspace to a Git repository doesn't automatically deploy changes to a live environment.
32+
- content: To sync content between the workspace and Git, ensuring they have the same content.
33+
isCorrect: true
34+
explanation: Correct. Connecting a Fabric workspace to a Git repository allows for synchronization of content between the two, ensuring they have the same content.
35+
- content: To allow multiple developers to work on the same code simultaneously without conflicts.
36+
isCorrect: false
37+
explanation: Incorrect. While Git does allow multiple developers to work simultaneously, the connection of a Fabric workspace to a Git repository isn't primarily for this purpose.
38+
39+
40+
- content: What is the primary function of deployment pipelines in Fabric?
41+
choices:
42+
- content: Deployment pipelines are used to create new content in Fabric.
43+
isCorrect: false
44+
explanation: Incorrect. Deployment pipelines don't create content. They automate the movement of content through different stages.
45+
- content: Deployment pipelines are used to delete old content from Fabric.
46+
isCorrect: false
47+
explanation: Incorrect. Deployment pipelines don't delete content. They facilitate the testing and updating of content.
48+
- content: Deployment pipelines automate the movement of content through the development, test, and production stages.
49+
isCorrect: true
50+
explanation: Correct. Deployment pipelines in Fabric help to automate the process of moving and updating content across different environments.

‎learn-pr/wwl-data-ai/implement-cicd-in-fabric/8-summary.yml

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn-wwl.implement-cicd-in-fabric.summary
3+
title: Summary
4+
metadata:
5+
title: Summary
6+
description: "Summary"
7+
ms.date: 11/8/2024
8+
author: wwlpublish
9+
ms.author: theresai
10+
ms.topic: unit
11+
durationInMinutes: 1
12+
content: |
13+
[!include[](includes/8-summary.md)]

‎learn-pr/wwl-data-ai/implement-cicd-in-fabric/includes/1-introduction.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
As a Fabric data engineer or developer, you're responsible for designing, building, and maintaining Fabric items that store, process and, analyze data. You collaborate with your team to release changes from development through production in different Fabric workspaces. With multiple engineers working on projects, there's a need to incrementally release and integrate Fabric item changes and move those changes through a deployment process where they can be tested and quickly released. Lifecycle management in Fabric lets you do this.
2+
3+
Lifecycle management in Fabric uses deployment pipelines and source control integration to help you achieve continuous integration and continuous delivery (CI/CD). You can integrate Fabric with version control systems like GitHub and Azure DevOps and improve your delivery process, and integrate automated testing.
4+
5+
By the end of this module, you'll know how to work with source control in Fabric, how to use Fabric deployment pipelines and how Fabric REST APIs can be used for CI/CD automation.

‎learn-pr/wwl-data-ai/implement-cicd-in-fabric/includes/2-understand-cicd.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
When you and members of your team are each responsible developing and maintaining different parts of your Fabric environment, a best practice is to work in isolated development environments until you're ready to combine your development efforts and publish your changes to a particular pre-production environment. When you're ready to publish your changes, you need to make sure that your changes don't break existing code or interfere with changes made by other developers. There's also a need to ensure that code changes are saved and can be reverted if there are issues. The built-in continuous integration and continuous delivery capabilities in Fabric can help facilitate this.
2+
3+
Continuous integration and continuous delivery is a process for integrating code contributions from multiple developers into a main codebase. Contributions are frequently committed, and automated processes build and test the new code. Code is continuously moving into production, reducing feature development time.
4+
5+
### Continuous integration
6+
If developers work on separate code branches on their local machines for long periods of time and only merge their changes to the main codebase once their work is finished, this increases the likelihood of conflicts and bugs that might only be identified in later development stages and can slow down delivery of features to users.
7+
8+
Continuous integration (CI) helps you avoid bugs and code failures and lets you continuously develop and release functionality. In CI, you frequently commit code to a shared code branch or trunk in a version control system and once it's merged, changes are validated by a build process and automated testing. Conflicts between new and existing code are identified earlier in the development process and are easier and faster to fix.
9+
10+
### Continuous delivery
11+
Continuous delivery happens after continuous integration. Once CI is complete, code is deployed to a staging environment where more automated testing is performed before code is released into production.
12+
13+
### Continuous deployment
14+
Continuous deployment is a process that automatically releases updates into production environments through structured deployment stages, once they pass automated tests.
15+
16+
## Use CI/CD in Fabric
17+
Managing the lifecycle of Fabric items using CI/CD has two parts: integration and deployment. Integration is implemented using Git. Deployment is implemented using Fabric deployment pipelines. Automation of deployment or integration is implemented using Fabric REST APIs.
18+
19+
- **Git:** Lets your team collaborate using branches, and provides version control. It helps you manage incremental code changes, and see code history.
20+
- **Deployment pipelines:** Lets you promote code changes to different environments like development, test, and production.
21+
- **Fabric REST APIs:** Enables automation and lets you programmatically manage CI/CD processes.

0 commit comments

Comments
 (0)