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
It's 2022 and it's very common to deploy to multiple machines? Is this not supported?
We have redundant prod machines and would like to be able to deploy to all of them in one parallel step. Not through a multi-step process which is very tedious and time consuming.
I'm trying to do something like this - and would like to see one "Promote" button to push to deploy to both Prod environments but instead I seem to be forced to deploy to Prod 1, then Prod 2.
Would be nice if there was a trigger at the parallel level which would then kick off all the parallel steps together.
name: Deploy to Production 1
deployment: Production 1
name: Deploy to Production 2
deployment: Production 2
Hello @Jim Priest ,
Welcome to Atlassian Community!
From my understand you would like to have the option to trigger multiple manual parallel steps using a single button. If that is the case, unfortunately at this moment this option is not available on Bitbucket Pipelines. However, we already have a feature request on our public issue tracker to implement that functionality, which you can find in the following link:
I went ahead and linked this post to the feature request, but I would also suggest you to add your vote there, since this helps both developers and product managers to understand the interest. Also, make sure you add yourself as a watcher in case you want to receive first-hand updates from that ticket. Please note that all features are implemented with this policy in mind: https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html
Let us know in case you have any questions.
Thanks, @Jim Priest .