Skip to main content

Using an environment variable to define a path when using the Docker executor

Overview

In some cases you may need to use an environment variable when specifying a path. For example: source ${CIRCLE_WORKING_DIRECTORY}/script.sh which will expand to the string literal ${CIRCLE_WORKING_DIRECTORY}/script.sh when using the Docker executor.

Example error:

Screen

Resolution

    1. You can use the pwd command. Example: source $(PWD)/script.sh.

    2. You can use the eval command. Example: source $(eval echo ${CIRCLE_WORKING_DIRECTORY}/script.sh)

    3. Add the following run step to your build:

 - run:  
     name: "Fix CIRCLE_WORKING_DIRECTORY"  
     command: echo 'CIRCLE_WORKING_DIRECTORY="${CIRCLE_WORKING_DIRECTORY/#\~/$HOME}"' >> $BASH_ENV

Additional Resources:

Related Articles
How to pass environment variables between jobs
How do I run commands in the remote Docker environment and understanding how this mirrors Docker in Docker?
How to Pass Environment Variables Between Steps in CircleCI
Accessing Environment Variables in Windows Executor on CircleCI
Installing Microsoft Edge Browsers for E2E Testing on Docker Executor
Did this answer your question?