pipeline: how to build for multiple environments?

Question

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

Patrik S · Answer

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:

* https://support.atlassian.com/bitbucket-cloud/docs/pipeline-triggers/

Admin Admin_zz7tsr · Answer

@Patrik S

thank you.  A few clarifications:

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

Patrik S · Answer

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.