Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bitbucket pipelines does not substitutes deployment variables in all places.

Shoaib Khan June 20, 2022

Hi, 

 

When I'm running my pipelines, all the deployment variables show up when I use "env" command this includes the namespace which I'm passing as ${OC_PROJECT}. But later in same script when I use it during deployment, its value doesn't get populated there. Because of which I'm getting errors during deployments.

helm upgrade -n ${OC_PROJECT} -i -f charts-config/.........3.JPG1.JPG

 

1 answer

0 votes
Patrik S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 21, 2022

Hello @Shoaib Khan ,

Thank you for reaching out to Atlassian Community.

In order for us to investigate further, could you please share the bitbucket-pipelines.yml file of your build? 

Also, from the screenshot, it seems you are executing a script file inside your build. If that is the case, could you also share the section from the script where you are referencing the variable? Have you tried referencing the env variable with $OC_PROJECT instead of ${OC_PROJECT}?

Kind regards,

Patrik S

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events