Multi branch Pipeline in Azure Devops

Question

I am trying to build a YAML release pipeline in Azure DevOps for that I have created multiple branches to keep environment-specific files

I created 4 pipelines for release as well:

Problem: Whenever I am making any changes in any branch, all the branch pipeline starts running. If I run an individual pipeline it works fine.

# Starter pipeline
# Start with a minimal pipeline that you can customize to build and deploy your code.
# Add steps that build, run tests, deploy, and more:
# https://aka.ms/yaml

trigger:
- acc

pool:
  name: 'Agent'

steps:

- task: Kubernetes@1
  displayName: 'Deploy on  K8s Cluster'
  inputs:
    connectionType: 'Azure Resource Manager'
    azureSubscriptionEndpoint: 'vs-aks-sc'
    azureResourceGroup: 'azwe-rg-01'
    kubernetesCluster: 'azwe-aks-01'
    command: 'apply'
    arguments: '-f $(System.DefaultWorkingDirectory)/kubernetes/acc.yaml'

What you mean "If i run individual pipeline it work fine."? Manually run each pipeline? — Leo Liu, May 06 '21 at 02:24
Yes if i manually run each pipeline it work fine, howver if i change anything in branches present in azure repo all branch run the same pipeline — Satyam Pandey, May 06 '21 at 03:19
@SatyamPandey, Thanks for your reply. Need to confirm one more things, you said all branch run the **same** pipeline instead of "all the branch pipeline starts running", that mean those four branch run the same pipeline rather than their respective pipelines, am I right? — Leo Liu, May 06 '21 at 03:27
@SatyamPandey, you need make sure all those four pipeline use the respective YAML file used by the pipeline and the branch trigger set is the respective branch. For example, the pipeline `Deploy to Prod K8S Cluster` pipeline need use the YAML under the branch `Pord` and the branch trigger should be `trigger: - Prod` — Leo Liu, May 06 '21 at 03:39
Yes i have did the same how ever let me delete the pipeline and recreate the same — Satyam Pandey, May 06 '21 at 03:43
@Satyam Pandey, How about the issue? Does the answer below resolved your question, If not, would you please let me know the latest information about this issue? — Leo Liu, May 07 '21 at 09:29

score 7 · Answer 1 · answered May 06 '21 at 07:43

Problem: Whenever I am making any changes in any branch, all the branch pipeline starts running.

If you just want to run the corresponding pipeline of the branch you modified, you need to make sure set the pipeline with the YAML file in the corresponding branch and set the correct branch trigger.

For example, for the Acc branch:

We need create a YAML file under the branch Feature/TestSample-acc with the branch trigger in the YAML file:

trigger: 
  branches:
    include:
      - Feature/TestSample-acc

Then create a pipeline with existing Azure pipeline YAML file:

New Pipeline-> Azure Repos Git(YAML)-> Select your repository-> Select existing Azure pipeline YAML file:

Now, this pipeline only triggered by the modification on the branch Feature/TestSample-acc:

You could set the same this for other branches, like

trigger: 
      branches:
        include:
          - Feature/TestSample-dev

Besides, if you do not want to control the trigger by the YAML file, you could override it by the UI trigger settings:

This option is disable by default, so that we could control the trigger in the YAML file directly.

If you enable it, you just need to add the Branch filters for just one branch:

If I am not understand your question correctly, please let me know for free that what you want to achieve.

This should be accepted as the correct answer. Helpt me at least :) — Shogoot, Aug 04 '21 at 09:53

score 1 · Accepted Answer · answered May 05 '21 at 16:52

1

You should check the CI trigger setting of the pipeline to only allow it to trigger on your wanted branches

Change CI Trigger

answered May 05 '21 at 16:52

lylam

46
1

ohk i have made some changes i updated image in my question section – Satyam Pandey May 06 '21 at 04:20
When i disabled continues integration trigger in my pipeline, its not triggering automatically, – Satyam Pandey May 06 '21 at 04:25

score 0 · Answer 3 · answered Aug 18 '22 at 13:31

0

The answer by "Leo Liu-MSFT" is correct.

BUT you also need to make sure that on each branch the YAML file has a different name, otherwise a commit to a single branch triggers more than one pipeline build.

answered Aug 18 '22 at 13:31

Jose Marcenaro

53
4

Multi branch Pipeline in Azure Devops

3 Answers3