Curious if others are experiencing this as well. I've tried using different agent pools, eliminating all branch filters, etc.
#Release trigger no longer working?
obsidian schooner
craggy hamlet
Same here
obsidian schooner
@craggy hamlet
Can I ask you to post here confirming that you're also experiencing the same issue?
https://learn.microsoft.com/en-us/answers/questions/1035154/azure-devops-release-trigger-not-working.html
craggy hamlet
Done 🙂
obsidian schooner
@craggy hamlet, for your awareness, I cut a ticket with MSFT via our EA so I'll let you know what they reply with
craggy hamlet
Nice, thanks
craggy hamlet
@obsidian schooner fyi you got an answer saying it wasn't the correct place to ask for it 🥲
Although the issue happens to be solved, my releases are triggering correctly now
obsidian schooner
@craggy hamlet I saw 😛 a bit frustrating but I did consider that might happen
Hopefully they start to add support for ADO over there
craggy hamlet
@obsidian schooner does it still work on your side ?
It went down again on mine
craggy hamlet
So on my side, releases are created ~1h after the build's done
obsidian schooner
Oof
I was told this morning by one of my devs that the release does end up triggering eventually, but very delayed
He saw all of our prior test builds deploy ~8 hours later
craggy hamlet
Wow
obsidian schooner
I also haven't received a response on my severity B ticket from Microsoft 😦
craggy hamlet
:/
obsidian schooner
Tempted to escalate to a severity A but will wait some time
I messaged them again
craggy hamlet
Ok
obsidian schooner
@craggy hamlet
https://status.dev.azure.com/_event/339589737
craggy hamlet
Thanks !