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:
Example of error:
Example of part of my bitbucket-pipelines.yml file with annotations:
I believe my question above is similar to this question:
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.
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
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