Power BI Integration with GIT --Solution Advise

[pradeep467]

Hi Friends,

I am trying to implement GIT integration into Power Bi and below is a solution that i have come up with and plannign to implement, would like to cross check with others that have implemented this in their organisations.

1. My understanding is PBI integration is only suppoted with Git repo hosted on Azure devops and not GIT on GITHUB (please correct me if this wrong).

2.  I have 3 workspaces 1 each for Dev, QA and Prod.

Implementaion plan:

Create a main branch and 3 child branches
Prod Branch <--> Main Branch (For inital sync and after every release to prod, sync prod to main branch )
Main Branch --> Dev Branch (For inital code syncup)

Dev Branch --> QA Branch (For ongoing devlopement)

QA Branch --> Prod Branch (For final Deployment)

Dev Branch is tagged to Dev workspace

QA Branch is  tagged to QA workspace

Prod Branch is  tagged to Prod workspace

Any ongoing development happens in Dev workspae and once chnages are completed , the developer pushes the code to Dev workspace. Dev branch detects a chnage and syncs up to Dev repo.

I am not doing a pull request from Dev to QA as that merges the entier dev code into Qa and some reports need to stay in Dev. So using the individual commits by developer in Dev branch for individual reports. I do a Cherry-pick request to push the required dev code to QA branch and then sync up the QA branch to QA workspace, same process is followed from QA to Prod.

Please advise if I am missing anything in this flow or if there is a better way to handle this. I am also looking for options to atomate the deployment. I evaluated deployment pipelines as an option but more inclined towards deployment through GIT as I can check what are the individual objct changes.

[KevinChant]

Something you might want to consider is to look to implement the Continuous Integration tests as well.

https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-build-pipelines?WT.mc_id=DP-M... 

[bcdobbs]

We use work items on azure devops boards. Developer creates a branch for that specific work item. Once complete they create a pull request into a test branch. Less reliance on cherry picking that way.

[pradeep467]

Thanks for the response Ben, so in your case if you have 4 developers, 4 separate workspaces need to be created for each developer? When pushing the work item, will that not replace the existing reports in workspace, beacuse before exploring the option of Cherry-picing I tried pulling a single wokitem but that deleted the rest of the reports in target.