Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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
4,456,778
Community Members
 
Community Events
176
Community Groups

pipeline: how to build for multiple environments?

Edited

hello,

 I understand that "deployment" allows the env specific variable values.

But what if I need to have an env specific variable value during the build?

e,g in "test", i need PORT=1000, but in "dev", PORT=2000.

 

I currently solved this by adding env specific vars, e.g PORT=$TEST_PORT, but the code is obviously will be quickly unmanageble

1 answer

0 votes
Patrik S Atlassian Team Jan 26, 2022

Hello @Admin Admin ,

 

In order to have different values for the same variable name, you can make use of the deployment variables.

You can create/manage deployment variables going to  Repository settings > Pipelines > Deployments.

Note: Deployment variables override both workspace and repository variables, and are unique to each environment.

In the example you provided, where you have the environments dev and test, once you create those environments in the repository setting,  you can configure a variable named PORT in each of them, but having different values.

Then, on your YML file, you would have to separate the scripts for each environment in two different build steps, and assign the corresponding deployment environment to each step as the below example :

- step:
name: My TEST env step
deployment: test
script:
- echo $PORT # print value of the variable PORT configured for TEST deployment environment
- step:
name: My DEV env step
deployment: dev
script:
- echo $PORT # print value of the variable PORT configured for DEV deployment environment

 

However, if your intention was to use just one step, and have different values for the same variable name, I'm afraid this is not currently possible, and in this case you would indeed have to use two variables(one for each environment) like $TEST_PORT and $DEV_PORT.

Hope that helps to address your questions.

Thanks, @Admin Admin 

Patrik S

Pateick,

Thank you.

The thinking is to have a general build step, that takes different values based On the branch type.

So that i dont have to Repeat the build code in several places.

Patrik S Atlassian Team Jan 26, 2022

Hello @andrew zyman ,

In case you are using the branch kind of pipelines, one option would be to write a script to set the environment variables at build time based on the name of the Branch who triggered the pipeline.

The script below makes usage of the $BITBUCKET_BRANCH default environment variable to check what is the name of the branch that triggered the build, and setup a PORT environment variable if the name matches one of the patterns dev.* or test.* .

if [ -z "$BITBUCKET_BRANCH" ]
then
echo "This pipeline is not using branches"
exit
fi
echo "Executing pipeline for branch: $BITBUCKET_BRANCH"

if echo "$BITBUCKET_BRANCH" | grep -q "dev.*"; then
echo "Dev branch"
export PORT=$PORT_DEV
elif echo "$BITBUCKET_BRANCH" | grep -q "test.*"; then
echo "Test branch"
export PORT=$PORT_TEST
else
echo "No matching option for branch name $BITBUCKET_BRANCH"
fi

The script above is creating an generic env variable called PORT with the content of  a repository variable , in this case either $PORT_DEV or $PORT_TEST , so your further steps in the build can always use $PORT.

Then you could run the  script on your YML file like below: 

pipelines:
 branches :
'**' :
- step:
script:
- chmod 700 env_script.sh #grant execute permissions to the script
- source ./env_script.sh #run the script to set env variables
- echo $PORT #print the env variable
Thanks, @andrew zyman .
Patrik S.

@Patrik S 

thank you.  A few clarifications:

Is it correct to understand that "**" == "default" in branch-based pipelines?

Patrik S Atlassian Team Jan 31, 2022

Hello @Admin Admin 

The "default" keyword is also considered a branch-based trigger, so your assumption is correct.

'**' will match all branches.

For more details about pipeline triggers you can refer to the following documentation:

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events