Chapter 17. CI/CD in Microsoft Fabric
Continuous integration (CI) and continuous deployment (CD) are crucial concepts in the modern software development workflow. When implemented properly, CI/CD processes enhance the software or data delivery workflow and enable faster, more reliable, and more frequent releases, ensuring high code quality and developer efficiency.
If we take a look into CI/CD concepts with our Fabric lens off, we might conclude that CI represents the practice of regularly integrating (merging) code with the rest of the organization and that CD is a set of practices to always keep your application in a deployable state, usually implemented through a pipeline, which ensures that all changes go through a series of test environments before culminating in a production deployment.
CI/CD Workflow Options
Before we examine particular features and concepts for implementing effective CI/CD workflows in Microsoft Fabric, let’s first take a step back and explain how these concepts fit into the big picture of the more generic lifecycle management concept. In a nutshell, lifecycle management enables an effective workflow for releasing products quickly by continuously delivering up-to-date content into production, while maintaining the ongoing development of new features and bug fixes and ensuring they are deployed using the most efficient delivery method.
We can identify three main components of lifecycle management in Microsoft Fabric:
-
Git integration is a CI part of the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access