Steps to publish an ADF pipeline

  1. Make changes in the development branch
  2. Submit a PR request
  3. Inspect the code changes
  4. Approve the PR request

This will merge the Pull request  – which is essentially taking the dev branch and merging it into the master branch

Machine generated alternative text:
added wait 
Overview 
O 
3e2b4ae6-838d-4071-3076-Se6010b91SS0 e3047cd9-ea0e-4bff-bbff-dcc87fd2e6bb development into master 
Files Updates Commits 
Merging pull request 
No merge conflicts 
Last checked 2m ago 
Description 
Updating pipeline: Copy from REST connector into ADLS Gen2

This should sync up the master branch and the development branch

If you try to directly publish from the development branch ,  it throws mud at you  – it says publish is only allowed from collaboration.

Machine generated alternative text:
Microsoft Azure Data Factory testdfsjvz 
merit •v 
/ C_) Refresh 
Factory Resources 
Pipelines 
Copy from REST connector i.. 
pipelinespec± 
pipelinetocc.pytc.avrc 
Datasets 
Data flows 
Templates 
Copy from REST con... 
Activities 
Move & transform 
Azure Data Explorer 
Azure Function 
Batch Service 
Databricks 
Data Lake Analytics 
General 
HDlnsight 
Iteration & conditionals 
Machine Learning 
Seve as template 
Valid-te 
> Debug 
•cid trigger 
Cac•y "t: 
CopyD?ts 
GetSearerToken 
Publish is only allowed from collaboration ('master') 
branch. Merge the changes to 'master'.

5. Switch to master branch and then hit publish

This is actually deploying the ADF pipeline to the service , so  it automatically internally kicks of a validation and will prompt you fix the validation errors.  If you have already validated the data factory job then you are good to go and this will publish the flow.

The publish branch is the branch where all of the arm templates are stored. The other branches dont have these and you may get a prompt indicating the same .