Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Use duplicate environment in the same pipeline (Bitbucket Pipelines)

I have three deployments environment Test, Staging and Production. Each one has some environment variables that the another also has (e.g. DEPLOY_URL). DEPLOY_URL has a different value per deployments environment. 

Actually, we can't have the deployment keyword duplicate in the pipeline definition.  I wanna know how can I achieve this in another way. This is because I have a step that deploy the application (Step One) and another that trigger a service based on the current deployment (Step Two). 

For example:


- step: &stepOne
name: Run Step One
- ... commands

- step: &stepTwo
name: Run Step One
- ... commands
- step:
<<: *stepOne
deployment: Production
- step:
<<: *stepTwo
deployment: Production
- step:
<<: *stepOne
deployment: Staging
- step:
<<: *stepTwo
deployment: Staging


2 answers

1 accepted

2 votes
Answer accepted

Sadly, this can't be done yet.

If you want to use deployments, you will have to merge your steps into one.

Actually, there's an open issue on Atlassian's Jira:

I'm facing the same problem right now, trying to figure out how i can organize things better without deployments.

In summary:

- Multiple steps (parallel or not) = don't use deployment

- Single steps = use deployment

That's what i found researching through community forums, hope this helps!

Waiting for Atlassian Team to implement this.

Thanks @Sergio Flores 

I will implement it as you suggest. 

While this isn't a solution, it might help you think of your issue a bit differently. I, too, ran into this problem as I broke up my pipeline into steps. When I realized I couldn't put the "staging" or "production" deployment marker on all the steps, I paused and remembered the value deployment markers bring to my workflow.

My number one reason for deployment markers is so I can trace a deployment back to the Jira issues that were part of it. This helps me author release notes, etc. This all led me to place the deployment marker on the step that builds the Docker image with the new code and publishes it to Amazon ECR. All the other steps in the pipeline didn't really have a direct impact on the code that was just moved. 

Hope this helps in some way. And sorry I'm so late to the game - wanted to see if my $0.02 can help.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

New improvements to user management in Bitbucket Cloud 👥

Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...

3,736 views 10 16
Read article

Community Events

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

Events near you