Skip to main content
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.

Reply
vegardbus
New Contributor

Git support for scheduling of data pipelines?

Hi! My team has connected our workspaces to Git. 
Currently our experience is that when we create data pipelines, the data pipelines themselves are synced to Git. However, when we equip the pipelines with scheduled runs at specific times, these are not tracked by the source control and are thus not included in the Git branch. 

Is this a known limitation, or would it seem like we are doing something wrong? I have not been able to find any documentation describing this limitation, if so. 

4 REPLIES 4
AndyDDC
Valued Contributor

Anonymous
Not applicable

Hi @vegardbus ,

 

Thanks for the reply from AndyDDC .

 

While the data pipeline itself can be synchronized to Git, plan runs are not automatically included in the Git branch. You need to manually manage schedule runs for the pipeline outside of the Git repository.

 

You can provide feedback on this feature on Home.

 

Best Regards,
Yang
Community Support Team

 

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

chancl
New Contributor

Hi, just checking if there are any updates on this. I've just tried and it seems like schedules aren't exported to git along with the data pipeline, and I couldn't see it on the road map. Any work arounds that isn't manually setting it up in the UI?

caseybks
New Contributor II

Hi,

 

Just wondering what you have done with git branches and schedules please?

 

I don't know if this has been introduced since your post, but I can see schedules being backed by git now in my repo. However, my issue is that when people create a new branch from develop, they are also copying the active schedule into their branched workspace too. Therefore the pipeline is scheduled to run in all the branches workspace, which is the issue. We can tell people to turn the schedules off manually in their workspaces but this is annoying and people may forget. Just wondering if you are experiencing this too? 

 

 

Helpful resources

Announcements
Users online (9,586)