All pipelines in Azure DevOps are triggered when there is a commit to the Repo

Copper Contributor

Hello,

 

Our team uses the Mono Repo concept in Github, where multiple teams contribute to the code and reuse any modules that are developed by other teams. So there are multiple pipelines triggered based on the path like an application. So if one team commits to a particular path, the other pipelines present in the repo are also triggered even though it is in a different location and outside the build folder. 

 

e.g.

 

Commit was in path here (apps/dotget/core-jss):

 

trigger:
  branches:
    include:
      - master
  paths:
    include:
      - apps/dotget/core-jss
      - shared/**/*.contentType.ts
      - shared/disclaimer/**/*.ts

 

But another pipeline was also triggered which is not in the build path:

 

 

trigger:
  branches:
    include:
      - master
  paths:
    include:
      - apps/infra/mongoDB/tf/

 

 

We have multiple triggers like this for different pipelines.

 

 

Thanks,

Sundar.

0 Replies