You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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/.........
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.