You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have a pipeline that automatically updates an Azure web site. If we push too fast to this repo then the deployment is paused. Is there a way to turn off the deployment concurrency control? Obviously we don't want multiple deployments to happen in parallel, but it's ok if it happens right after each other, since we pushed multiple commits (that each triggered the pipeline). I just expect it to deploy the last commit at the end.
I'm afraid that it is not possible to disable this at the moment.
We have a feature request for the automatic resuming of paused deployment steps:
As per the latest update from one of our product managers, this is something we plan to deliver in the future, but we don't have an ETA yet. You can add yourself as a watcher to that feature request (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.
In the meantime, you can check the script that another customer developed (using our APIs) which checks for paused deployments, and in case the last deployment is paused, it triggers a new build:
You can take a look, and if it would be helpful for you, you can adjust it to your use case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.