Setting environment variables per branch in Gitlab CI or “a poor man’s dotenv”

Phillip Kessels
May 15, 2019 · 1 min read

Often times a different set of environment variables is needed when executing jobs in Gitlab CI depending on the branch we are on. The following is a real life example for the website of our shift scheduling software at tiftapp.com.

We build our website with Hugo and deploy it to different subdomains. From our develop branch we want to deploy to staging and from master we want to deploy to production.

In the past we scattered some test commands around our deploy script, however when our build stage required one of the environment variables as well we decided for a more concise way.

# .gitlab-ci.yml
before_script:
- source .${CI_COMMIT_REF_NAME}.env
# ...

We simply source environment variables from the .develop.env and .master.env files.

# .master.env
export DOMAIN='tiftapp.com'
export FTP_DIR='staging'
export FTP_HOST='tiftapp.com'

Discussion

  • a single source of truth makes it easy for developers to add new and find existing configuration
# .master.env
export FTP_PASS="$PROD_FTP_PASS"
export FTP_USER="$PROD_FTP_USER"

spacepilots

agency for digital service experience

Medium is an open platform where 170 million readers come to find insightful and dynamic thinking. Here, expert and undiscovered voices alike dive into the heart of any topic and bring new ideas to the surface. Learn more

Follow the writers, publications, and topics that matter to you, and you’ll see them on your homepage and in your inbox. Explore

If you have a story to tell, knowledge to share, or a perspective to offer — welcome home. It’s easy and free to post your thinking on any topic. Write on Medium

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store