DevOps Stack Exchange is a question and answer site for software engineers working on automated testing, continuous delivery, service integration and monitoring, and building SDLC infrastructure. It only takes a minute to sign up.
Sign up to join this community
I have a Repository in Azure Repos which has branches as master, build, feature. Build Branch and Feature branches have their own pipelines code in the azure-pipelines.yaml in the branch itself respectively. So that they can have their dedicated pipelines
The problem is that When I commit to the Build branch or in the feature branch then, both the pipelines are triggered.
I have written in my azure-pipelines.yml
trigger:
branches:
include:
- build
exclude:
- feature
If you have set a CI trigger make sure you have set the filter to the exact branch which you need the build to be triggered and not the entire repository which is the default case.
You might consider using the pipeline trigger YAML override feature.
Go to the pipeline designer/editor view. Next to the "Run" button is the ellipsis. From that menu, select "Triggers". From the "Continuous Integration" section, you can choose "Override the YAML continuous integration trigger from here". Then you can tailor the pipeline triggers very specifically without the need to define them in the YAML.
build branch "include" only the build branch in the filter list. Then have the feature branch Exclude the build branch in the filter list. This should allow arbitrary feature/* branches to build only on the right pipeline.