CODEWITHSUNDEEP
azure-devops
Kostas Konstantinidis
Kostas Konstantinidis

Reputation: 13707

Azure Devops Pipeline won't trigger after a Pull Request merge

This is most peculiar.

I got this repository and pipeline. The pipelines are based on Yaml.

Here are the triggering definition:

trigger:
  batch: true
  branches:
    include:
      - "*"
  paths:
    include:
      - api/
      - devops/build/azure-pipeline-backend.yml
      - devops/build/stages/build-backend-stage.yml
      - devops/build/stages/deploy-backend-stage.yml

This repository has a branch policy to get changes verified before allowing them to be completed. The above pipeline triggers for all branches including Pull Request checks. It won't trigger for the default branch though after a pull request completion.

The triggers have not been overridden and they should follow the ones defined above. enter image description here

I've setup another repository and tried a similar setup and the triggering works fine so I am beginning to think that there may be some policy or something elsewhere that I am not aware of.

Upvotes: 2

Views: 2638

Answers (1)

bryanbcook
bryanbcook

Reputation: 18138

It appears as though your path filters are not matching the changes.

Add a wildcard to the api/* path

trigger:
  batch: true
  branches:
    include:
      - "*"
  paths:
    include:
      - api/*
      - devops/build/azure-pipeline-backend.yml
      - devops/build/stages/build-backend-stage.yml
      - devops/build/stages/deploy-backend-stage.yml

Upvotes: 0

Related Questions