Azure DevOps CI (push) triggers not working

[milos_cancarevic]

A few days ago, my Pipeline CI push triggers stopped working in Azure DevOps. I've recreated the webhooks in Bitbucket (noticed the change in API version to 7.1) but still doesn't work.

[milos_cancarevic]

Seems like CI is working again. Check it.

[Matt Sugden]

Ours is working again now.

[oeh]

Ours seems to be as well. Cheers

[Scott Rapsey]

Ours seems to be working now too

[Matt Sugden]

Same here. Last Wednesday (9th Feb) was the last time I saw an automatic build in devops.

[Scott Rapsey]

Same here, also stopped on the 9th of Feb 

[oeh]

We are having the same issue, anybody got any ideas on how to fix this?

[Matt Sugden]

If none of us have changed anything, but all our pipelines stopped at the same time, sounds like something has changed either in devops or bitbucket, don't know which one though.

I raised an issue with devops services support on Monday, not heard anything back yet.

[Vasile Sumanschi]

We are having the same issue. It started happening on 9th Feb. 

The pipelines respond to the creation/update of a Pull Request but not the merge of the Pull Request.

The bitbucket webhooks ( that were automatically added by azure devops during the pipeline creation ) appear to be called successfully ( there is a 200 status returned by azure ), however the pipeline is only triggered automatically when a PR is created/updated and not when it is merged.

---

https://support.atlassian.com/bitbucket-cloud/docs/troubleshoot-webhooks/

[Sebastian Brown]

We are having the same issue. It appears to have started around the 9th of Feb.

[Pavan Josyula]

we are facing the same issue only few builds are getting triggered 

[Jayden Maalouf]

Same issue here.
Tried copying the Webhook payload and manually triggering the pipeline using the payload - still no dice.
Something has definitely changed.

[Alex Billson]

Having the same issue in our environment, have tried the resolution steps mentioned in this post and I've seen it work once at most. Having to resort to manually kicking off the builds for the time being

[oeh]

I’ve just got my environment to work, I took these steps:

1. Select Pipelines from the left menu
2. On the Pipelines page, click the 3 dots on the right and select “Manage security”
3. At the bottom left under Users is the Build Service user, I selected this and then changed the “Queue builds” option from “Not set” to “Allow”.
4. One pipeline seem to work straight away another I had to save it a couple of times but it then started to work.

Hope this works for you.

[milos_cancarevic]

It didn't work for me, unfortunately.

[oeh]

It is actually really temperamental for me now, sometimes it runs and sometimes it doesn't.  It is such a pain in the butt.