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 several Staging and Production environments, in different regions, and the versions we deploy on each region could be completely different.
In the image below you can find how we want to deploy:
As you can see in the image above, for each version that is built in QA, we want to choose if we want to deploy it in Staging-EU, Staging-US, or Staging-Asia. And then, from that environment, it will go to its corresponding Production environment, in the same region.
Unfortunately, we are struggling to handle something like that with the current implementation of the Bitbucket Pipelines and Deployments, because it forces us to deploy/promote the same version in all Staging environments before going to Production.
In other words, it forces us to deploy in this way: QA -> Staging-EU -> Staging-US -> Staging-Asia -> Prod-EU -> Prod-US -> Prod-Asia.
The only solution we have found is to create a different branch per region: EU, US, ans Asia, and merge from master to those brances. But the solution looks over complicated to me.
Is there a better way to implement this?
Thanks in advance.
Hi Ernesto and welcome to the community!
If you have a pipeline with seven steps (QA, and six for the Staging and Production regions), there is no way to skip a step in the middle and execute another one that comes after that.
We have a feature request for the ability to skip a step in a pipeline that you can vote for
Another approach would be to create three custom pipelines, one per region, each one with a Staging step and a Production step:
You could then trigger manually the custom pipeline for the region you want.
Custom Pipelines do not run automatically when you push to a certain branch. They can be triggered manually in one of the following ways:
Would something like that work for you?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.