Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×In case you're referring to manual steps, please find this feature request:
Hmm, for me normally on branch commit (and push) the branch pipeline automatically runs for that commit. What am I not seeing here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What if Atlasssian would watch for the deployments and take the very latest one based on the git commits. Deploy that one and discard the other paused deployments?
What do you guys think? Just chiming in :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Why not schedule a pipeline that just does this via the REST API? I think the trick is to have an automated deployment step (not one that is with the manual flag).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.