Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

How to use deployment variables in multiple steps

I wanted to configure my Pipeline to build my production assets and then deploy them but I'm struggling to make the Deployment variables accessible to multiple steps.

I thought I would just duplicate the deployment property to all the steps that require it but that throws a config error and won't start the pipeline.

I think I also need to:

  • Use a node image to build the assets.
  • Use an AWS image to deploy.

 

Example of error:

Screenshot 2020-01-24 at 12.21.13.png

 

 

Example of part of my bitbucket-pipelines.yml file with annotations:

Bitbucket_Pipelines_-_Validator.png

 

I believe my question above is similar to this question:

https://community.atlassian.com/t5/Bitbucket-questions/Usage-of-Deployment-variables-on-multiple-steps/qaq-p/1103443

1 answer

Have you find something about it? 

To get around this I ended up moving all my variables from deployment-variables to Repository-level-variables with more verbose names for each deployment type.

This way the variables are accessible in the various places I need them.

I duplicated my singular "build" script within my bitbucket-pipelines.yml but replaced all the  variable names. So now I have 2 scripts "build-for-production" and "build-for-staging" which are identical apart from the variable names.

 

It's not ideal because of all the code duplication but I don't think there's another way in February 2020.

Like # people like this

Suggest an answer

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

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

995 views 20 11
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