How to use deployment variables in multiple steps

[Mark Stickling]

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:

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

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

[cvivieca]

Have you find something about it? 

[Mark Stickling]

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.

[Loris D'Antonio]

You might be interested in voting for : https://jira.atlassian.com/browse/BCLOUD-18261