If there are several pushes to a repo, the last pipeline will get paused for us at the deployment stage, if the previous pipeline's deployment is in progress.
Makes total sense to not mess up the deployments. However it's inconvenient to go and manually check all pipelines for successful completion. Especially if there's a large number of pushes.
Actually, like Rick, de deployment IS automatic. But it cannot run concurrently. The current behaviour makes it so that the oldest concurrent commit makes it to the environment, while what you want is de most recent. As such, the pipeline should auto-unpause as soon as the previous deployment is done for the environment, instead of waiting for a manual unpause.
We should be able to enable this kind of behaviour within the settings of bitbucket, without requiring external tooling.
Hi everyone, Are you Bitbucket DC customer? If so, we'd love to talk to you! Our team wants to dive deep to understand your long-term plans regarding Bitbucket DC and Atlassian Cloud. Do you plan...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events