Best Practices to for Fabric / Azure DevOps CI/CD.

[Amiral]

What is the best practices today to implement DevOps structure - CI/CD using Azure DevOps ? 
example : features Branch (per developer) -> FT WS(per developer)
Dev branch -> ws-Dev,
Test branch -> ws-Test,
Prod branch -> ws-Prod

As Fabric Admin is that possible to limit the storage/ CPU's for each workspaces ?
is the shortcuts are fully supported with Fabric DevOps ? what are other items not fully supported ?

[v-nmadadi-msft]

Hi @Amiral,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the community members for the issue worked. If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Thanks and regards

[v-nmadadi-msft]

Hi @Amiral,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If our responses has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[v-nmadadi-msft]

Hi @Amiral,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[Amiral]

What is the best practices today to implement DevOps structure - CI/CD using Azure DevOps ? 
example : features Branch (per developer) -> FT WS(per developer)
Dev branch -> ws-Dev,
Test branch -> ws-Test,
Prod branch -> ws-Prod

As Fabric Admin is that possible to limit the storage/ CPU's for each workspaces ?
is the shortcuts are fully supported with Fabric DevOps ? what are other items not fully supported ?

[suparnababu8 · Accepted solution]

Hello @Amiral 

If you are Fabric admin, you can restrict and manage the resources of a workspace. set the storgae quotas for every workspace to control the amount of data that  can be stored/used.  for each workspace, limit the the cpu usage in workspace from consuming excess resources.

Yes, some of the items are not supported. Shortcuts are not tracked in Git integration for lakehouses. The Microsoft documentation states that “Only the Lakehouse container artifact is tracked in git in the current experience. Tables, folders, shortcuts and other metadata changes aren’t tracked and versioned in git.

Pls go thorugh below documentation. It might helps you

https://learn.microsoft.com/en-us/fabric/cicd/manage-deployment

https://learn.microsoft.com/en-us/fabric/cicd/git-integration/intro-to-git-integration?tabs=azure-de...

https://community.fabric.microsoft.com/t5/Fabric-platform/Shortcuts-not-supported-by-deployment-pipe...

Thank you!!!

Did I answer your question? Mark my post as a solution!

Proud to be a Super User!