Forum Discussion

caseybks's avatar
caseybks
Advocate III
11 months ago
Solved

Git Branching with active Schedules

Hi,   We are using git integration with our development environment workspace. Develop is our collaboration branch from which the data engineers create a feature branch from. Their feature branch i...
data engineering
data pipeline
  • caseybks's avatar
    caseybks
    11 months ago

    Hi Anonymous,

     

    Haha, yes it does feel like someone has gone git happy 😄 I wish they'd focus on Lakehouse git version integration instead.

     

    Yes, we've gone for a similar solution. In the develop branch, which is the branch we all pull from, we have the committed versions of the schedules turned off, but then turn them back on in the workspace. So unfortuantly we have to live with the uncommited icon noficiations in the workspace, which is annoying, but we can live with.

     

    Only our Dev workspace is backed by git, the develop branch. The code is pushed into other workspaces by our DevOps deployment pipelines. Or you can use the Fabric deployment pipelines too. So turning on/off schedules in Dev workspace does not affect the test and production workspaces.

v-achippa's avatar
v-achippa
Community Support
11 months ago

Yes enabling or disabling schedules directly in the workspace can cause diffs. The best way is that keep all schedules disabled in git across all branches. Then after deploying to Test/Prod via a deployment pipeline, enable the schedules at runtime in the workspace without committing that change back to git.
This way Dev/feature branches remain clean and only the Test/Prod runs the schedules, avoiding unwanted diffs.

 

Thanks and regards,

Anjan Kumar Chippa

v-achippa's avatar
v-achippa
Community Support
11 months ago

Hi @caseybks,

 

We wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.

 

Thanks and regards,

Anjan Kumar Chippa