nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Using deployment variables in other steps

Neil Nand

Hello,

I've split my deployment into two steps, one step for building + deploying code and several other steps, which run in parallel, to run some commands needed for deployments against different databases.

What I'd like to do is set some environmental variables at the deployment level and use them as environmental variables in steps that are not part of the deployment as we unfortunately cannot have multiple steps in a single deployment. How would I go about this?

Tl;Dr
I'd like to use environmental variables set at a deployment level in steps not part of that deployment.

Accepted answers

Daniel Santos_157bm4

Hi @Neil Nand

I'm not sure if I really got what is your intent with this configuration.

Can you share a little bit more on what problem you are trying to solve?
How the steps that would consume the deployment variables would be triggered?
Why repository variables are not an option for you?

Sorry for the questions, I just want to understand better your scenario to see if I can come with an option for you to move forward.

All comments

Daniel Santos_157bm4

Hi @Neil Nand

I'm not sure if I really got what is your intent with this configuration.

Can you share a little bit more on what problem you are trying to solve?
How the steps that would consume the deployment variables would be triggered?
Why repository variables are not an option for you?

Sorry for the questions, I just want to understand better your scenario to see if I can come with an option for you to move forward.

Neil Nand

Hello @Daniel Santos and thanks for the reply.

So the problems I'm trying to solve are:

* Current I'm using repository variables and an export command like the following but as these environmental variables are deployment environment specific it feel like it should be kept there and so I don't have such a large list of environmental variables that are both generic and for each deployment environment.

export DATABASE_HOST=$TEST_DATABASE_HOST

* That export code above is needed in many steps which is making the bitbucket-pipelines.yml file quite long and I'm looking for ways to trim it down.

* Currently these variables are triggered automatically as part of a branch pipeline. In this pipeline unit tests are run, then code deployed to server then the parallel steps to run commands are run on that environments DB and this is where I'm looking to use the deployment environmental variables.

Currently the setup I've got using the repository environmental variables works but I'm looking for ways to tidy this all up a little.

Daniel Santos_157bm4

Hi @Neil Nand

Thank you for sharing! Now I have a better perspective of what you are trying to achieve.

Variables from deployments are limited to their step as you already noticed, but there is a way to transfer them via artifacts.

In the following example, the variables VAR1 and VAR2 are declared in the deployment section:

pipelines:
  default:
    - step:
        script:
          - echo "I'm building"
    - step:
        name: Deployment step
        deployment: ci-test
        script: 
          - echo "export VAR1=\"$VAR1\"" >> variables
          - echo "export VAR2=\"$VAR2\"" >> variables
        artifacts:
          - variables
    - parallel:
        - step:
            script:
              - . variables
              - echo "$VAR1"
        - step:
            script: 
              - . variables
              - echo "$VAR2"

I'm not sure if it helps a lot, but at least you don't need to declare them again on each parallel step, just load.

There is a feature request to add environment variables to bitbucket-pipelines.yml. If you think this would be a good thing in your case, please add yourself as a watcher and vote on this one.

[BCLOUD-17453] Setup environment variables in bitbucket-pipelines.yml

I hope that helps.

Neil Nand

Thanks for the response @Daniel Santos and sorry it has taken me so long to get back to you your suggestion has worked.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket-pipelines

atl-pipelines