CODEWITHSUNDEEP
azure-devopsazure-pipelines
Rogerio Schmitt
Rogerio Schmitt

Reputation: 1275

Trigger azure pipeline based on multiple file changes

I'm trying to trigger an Azure DevOps Build pipeline based on two files being changed simultaneously on my master repository, with the following trigger:

trigger:
  branches:
    include:
    - master
  paths:
    include:
    - '**/*task.json'
    - '**/vss-extension.json'

My folder structure for this repository is something like this:

repository:

|--run-stryker
   --vss-extension.json
   --other files here ...
  |--task
     --task.json
     --other files here ...

Yet changes to these files at the same time are not triggering my pipeline. What am I doing wrong here?

Upvotes: 0

Views: 7684

Answers (1)

Bartosz Pelikan
Bartosz Pelikan

Reputation: 1055

Unfortunately using wildcards like this in CI triggers is not supported at this moment. You can use * only at the end of paths but this is working the same as without this. Wildcards like this are working in file matching in tasks but not in path trigger. So you must use exact paths like:

trigger:
  branches:
    include:
    - master
  paths:
    include:
    - 'run-stryker/task/task.json'
    - 'run-stryker/vss-extension.json'

or using only folder paths like:

trigger:
  branches:
    include:
    - master
  paths:
    include:
    - 'run-stryker/*' # is the same as 'run-stryker/'

Documentation reference: Wildcards in CI triggers

Upvotes: 3

Related Questions