I need to automate Azure Data Factory deployment via Azure DevOps. As part of that, I have created a build pipeline but for enabling continuous trigger, which branch should I select? Is it the adf_publish branch? If this is the branch, then I believe a new build should be published manually in the Dev environment to trigger a change in the adf_publish branch, which is a manual process. Thanks in advance!!
2 Answers
0
votes
You should choose adf_publish branch when enabling continuous trigger. So that whenever changes are published to adf_publish branch, your pipeline will be triggered.
By default, data factory generates the Resource Manager templates of the published factory and saves them into a branch called adf_publish.
To trigger a change in the adf_publish branch, you need to click Publish to manually publish your code changes in the collaboration branch to the Data Factory service, after you have merged changes to the collaboration branch (master is the default). So the the changes will be updated to adf_publish branch.
You can refer to the examples in below blogs:
Continuous integration and delivery in Azure Data Factory
Continuous integration and delivery (CI/CD) in Azure Data Factory using DevOps and GitHub
0
votes
The above mentioned issue where dev values are hardcoded can be changed by adding parametrization template in the Azure DataFactory. Using the below link from Microsoft custom parameters can be added. https://docs.microsoft.com/en-us/azure/data-factory/continuous-integration-deployment#use-custom-parameters-with-the-resource-manager-template
