Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bitbucket pipelines does not substitutes deployment variables in all places.



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 Jun 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
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

2,245 views 2 9
Read article

Community Events

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

Events near you