While working on a test branch “release/v1.3” in our pipeline-templates repository, I noticed that CI was triggered on every pipeline using the templates. Even though the applications are using a different version of the templates.

How can I stop this from happening again?

I’ve found a possible solution here: Azure DevOps : how to disable CI trigger on a YAML template pipeline?
But won’t this disable all triggers?

So far, I’ve:

• Enabled the “Disable implied YAML CI trigger” option.
• Added “[skip ci]” to my commit messages.
• Included “trigger: none” in my pipeline-template repository.
• Verified that there are no tags on the pipeline-templates repository.
• Created a dummy branch test/test-deploy, which also triggered CI.

Application repository (BitBucket – .pipelines/deployment_pipeline.yaml):

trigger:
  tags:
    include:
      - v*
pr: none

resources:
  repositories:
    - repository: pipeline-templates
      type: git
      name: myproject/pipeline-templates
      ref: release/v1
extends:
  template: pipelines/deploy-service.yaml@pipeline-templates

Pipeline Template (Azure Devops Repository)

trigger: none

stages: ...
....