Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Usage of Deployment variables on multiple steps


I have broken down my pipeline in multiple steps to speed it up, and I'm using deployment variables to manage secrets:

- step:
name: Step1
deployment: test
- echo $DEPLOYMENT_CREDENTIALS > /tmp/keyfile.json
- parallel:
- step:
  name: Step2
   deployment: test
- echo $DEPLOYMENT_CREDENTIALS > /tmp/keyfile.json
- step:
name: Step3
deployment: test
- echo $DEPLOYMENT_CREDENTIALS > /tmp/keyfile.json


It looks like my pipeline it invalid, as it doesn't allow to specify "deployment" multiple times, however if I specify it only once the other steps do not find the variables. 

Is it possible to have multiple steps which make use of deployments ? Otherwise any suggestion on how to implement such scenario?




6 answers

we also facing same issue. we have steps like build docker image and push to ECR different AWS account. and another step we are publishing to the Kubernetes (again on different Kubernetes based on deployment).

``` - step: &deploy_set_env
name: "Deploy: Set Env"
enabled: false
- .env
- printenv | xargs -L 1 echo export > .env```


and then in the following steps:


- step: &deploy
name: "deploy"
- |
source .env


Like Jay Kravetz likes this

I used this approach but getting error in sourcing the .env file

bash: export: `%s': not a valid identifier

This worked well. However, the ability to tell multiple steps to use the same environment is necessary

Like # people like this

I'm facing almost the same issue. I was looking for some sort of environment variable that bitbucket is pushing by default (like BITBUCKET_DEPLOYMENT_ENVIRONMENT) in order to get the names of the steps in a pipeline. And I was thinking to use the one I mentioned but .... I need to declare fake environments in settings. Please let us use `deployment` or expose the name of the steps in an environment variable so that we don't need to repeat ourselves.

2 votes
Deleted user May 04, 2020

Here we are facing the same issue. This will be really nice to have.

Like # people like this
Deleted user May 05, 2020

Done. Thank you for pointing me that.

2 votes

Hello Nicola,

Currently, you can only define a particular deployment environment once per pipeline. In the example you have provided, you have used it in three steps. Which is why you're get errors in your pipeline.

You could try one of the following strategies. They have various trade-offs though.

  1. Consolidate the steps into a single one. Though, you'll lose the performance improvements you're trying to add.
  2. Create 3 separate environments, then reference each one once in each step. However, this will need duplicate environment variable configuration across the environments. And will also cause three Test environments to show in the dashboard, for what I assume is a single deployment?
  3. Set the Deployment credential as a repository-level variable. This will make it accessible to any pipeline that runs in the repository. But could have security concerns depending on how much trust other users with write access have.

You might also find these feature request interesting to follow: 

If neither of those cover what you'd like, you can also create a new feature request.

It would be helpful for us if you could add details of your use-case to one of those feature requests.



I have the same issues here. I have three steps to separate functionality but not be able to define the same deployment. This means that the variables that are need to all steps must either be defined elsewhere (very ugly and approach) or create a huge step (also ugly).

And I would like another problem that appears with this deployment limitation. I was using a python image in one step to achieve certain goals. And on the next step I was using another image. Having to merge the multiple steps to one means that I will have to do with one image for all of my goals in this step.

This should be fixed asap.

Like # people like this

Facing the exact same issue there. 
I've added more verbose env variables such as DEV_VARIABLE_NAME, PROD_VARIABLE_NAME in order to keep my multiple steps process.

Please consider fixing this ASAP :) 

Like # people like this

It would be great to be able to reuse the deployment variables.

Like # people like this

More than two years and still nothing?

Like # people like this

Still waiting for a fix.

Like # people like this

I'm having the exact same issue - waiting for a fix.

Like # people like this

Exactly the same issue, no acceptable solution to this yet.

Like Andy Honeycutt likes this

On the same boat, please allow deployment variables to be shared across steps.
Artifacts wont work for secret variables.

Like # people like this

Wow, more than 3 years and no update

Same issue.

When will we have a solution?

Is there any other way to achieve this?

Suggest an answer

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

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

2,084 views 2 9
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