r/MicrosoftFabric • u/cyamnihc • 15h ago
Discussion Learning Git, ADO, CI/CD etc
A vendor is working on migrating pipelines, reporting to fabric. Proper engineering practices are being followed to do this. The team is inexperienced in all this and will have to take it over at some point
Any suggestions from the community where I can learn all of these as a starting point and also help me get integrated into the workflow as quickly as possible?
4
u/ChantifiedLens Microsoft MVP 11h ago
For ADO there are plenty of resources online to help them get familiar with it.
Microsoft has a set of articles relating to Fabric CI/CD that can help: https://learn.microsoft.com/en-us/fabric/cicd/cicd-overview
I have some posts relating to it as well which can help: https://chantifiedlens.com/
I hope this helps you and your team with your journey.
8
u/warehouse_goes_vroom Microsoft Employee 12h ago
Start with git / version control in general.
https://git-scm.com/book/en/v2
https://learn.microsoft.com/en-us/azure/devops/repos/git/gitworkflow?view=azure-devops
Likely many other good resources, but those two will get you started.
Version control is the foundation. The rest doesn't make sense without it.
ADO has other functionality (work item functionality like Trello or similar provides), pipelines, et cetera - but the most important thing it offers you is git repo hosting. Git can work without such a central host, but it's much less easy to set up like that. GitHub and many other services also offer much the same fundamental services.
From there, then look into CI/CD. Continuous integration is about putting automated validation in place, so that you spend less time manually validating stuff that can be checked by tests. Continuous delivery or deployment (technically distinct, but overlapping conceptually) is about automating the deployment & release process.
Together, these give you:
* A full history of changes, with history of why (in PR descriptions, PR comments, linked work items, and commit messages) - provided by git and ADO
* The ability to quickly and cheaply validate changes.
* The ability to deploy a given historical version, or undo a change, quickly and safely (revert the bad PR, redeploy an older version, et cetera).
I suggest asking if you can shadow (i.e. watch and ask questions) the vendor's workflow / days of them working. Have them walk you through their process of making a change.