Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article presents developers with different development processes in Fabric, based on common customer scenarios. It focuses more on the continuous integration (CI) part of the CI/CD process. For a discussion of the continuous delivery (CD) part, see Fabric deployment options.
This article outlines a few distinct integration options, but many organizations use a combination of them.
Development process
The Fabric workspace is a shared runtime environment for all items, and each workspace can thus be connected to a single branch. Any changes made directly in the workspace override and affect all other workspace users. Therefore, Git best practice is for developers to have a seperate runtime environment - a different workspace. There are two ways for a developer to work in their own protected workspace.
- Develop using branched workspace. Each developer has their own workspace where they connect their own separate branch, sync the content into that workspace, and then commit back to the branch.
- Develop using client tools, such as Power BI Desktop for reports and semantic models, or VS Code for Notebooks.