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; } } }

Unable to get Deployment Variables

Oskar Kuklinski

My project uses a mix of Repository and Deployments variables. Repository variables are being fetched correctly but there is something wrong with deployment vars for each pipeline. Below I'm attaching my bitbucket-pipelines.yaml file and a setup in Repository settings -> Deployments

Echo script were only to check if the values are being passed.

BITBUCKET_DEPLOYMENT_ENVIRONMENT was empty while the rest were present in a

my_variables file

Accepted answers

Theodora Boudale

Hi @Oskar Kuklinski and welcome to the community!

I believe that the variable is empty because the syntax of the step is incorrect.

The following line can be used if you don't want to specify any additional values, like the step name and deployment environment.

- step: *env-specific-build-and-deploy

If you want to specify a different step name and deployment environment, the step should look as follows:

- step: 
    <<: *env-specific-build-and-deploy
    name: Some name
    deployment: stage

The step in the master branch pipeline needs to have a similar definition as well.

This is the documentation for reference (see section Override values)

https://support.atlassian.com/bitbucket-cloud/docs/yaml-anchors/

Could you give it a try and let me know if it works for you?

Kind regards,
Theodora

All comments

Theodora Boudale

Hi @Oskar Kuklinski and welcome to the community!

I believe that the variable is empty because the syntax of the step is incorrect.

The following line can be used if you don't want to specify any additional values, like the step name and deployment environment.

- step: *env-specific-build-and-deploy

If you want to specify a different step name and deployment environment, the step should look as follows:

- step: 
    <<: *env-specific-build-and-deploy
    name: Some name
    deployment: stage

The step in the master branch pipeline needs to have a similar definition as well.

This is the documentation for reference (see section Override values)

https://support.atlassian.com/bitbucket-cloud/docs/yaml-anchors/

Could you give it a try and let me know if it works for you?

Kind regards,
Theodora

Oskar Kuklinski

Hi @Theodora Boudale and thanks for looking into it!

Unfortunately after making a change mentioned above I am getting following error when running a pipeline (nothing else in console logs):

Screenshot 2023-05-02 at 13.22.37.png

Any idea why this could be happening? Also attaching updated bitbucket-pipelines.yaml file

Screenshot 2023-05-02 at 13.24.32.png

Theodora Boudale

Hi @Oskar Kuklinski,

I think the error occurs because of the indentation.

See my example:

- step: 
    <<: *env-specific-build-and-deploy
    name: Some name
    deployment: stage

For the lines below -step: I am using 4 spaces for indentation. In your yml file, it looks like the indentation is 2 spaces instead, which I believe is the reason for this error.

Kind regards,
Theodora

Oskar Kuklinski

Yes, that was indentation issue. Thanks for your help, pipeline runs successfully now!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud