Environment variables

Environment variables are useful for storing information that you do not want to store in the repository, such as your credentials or workflow-specific data.

Adding environment variables

You can add environment variables in App settings > Environment variables.

  1. Enter the name and the value of the variable.
  2. Check Secure if you wish to hide the value in the UI and build logs and disable editing of the variable. Such variables can be accessed only by the builder VMs during the build.
  3. Click Add.

To access a variable, add the $ symbol in front of its name. For example, access API_TOKEN by using $API_TOKEN. Note that it is required to use quotation marks with multi-line variables when you are referencing them in custom scripts, as shown in the example below:

> MY_VAR="var
> value"
> echo $MY_VAR
< var value
> echo "$MY_VAR"
< var
< value

Codemagic read-only environment variables

Codemagic exports several read-only environment variables during the build that you can use in scripts to customize the build process. Environment variables added by user will override Codemagic defaults. You can check which environment variables are exported by inserting the following script before or after any of the default build steps:

set -ex

Here you’ll find some of the read-only environment variables explained.

Environment variableValue
BUILD_NUMBERNumber of the build for this project in Codemagic
FCI_BRANCHThe current branch being built, for pull requests it is the destination branch
FCI_COMMITCommit hash that is currently being built by Codemagic, for pull request builds it is hash of the source commit
FCI_PROJECT_IDUUID of the project that is being built
FCI_BUILD_IDUUID of the build
FCI_TEST_STEP_STATUSTest step status, success or failure
FCI_BUILD_STEP_STATUSBuild step status, success, failure or skipped
FCI_BUILD_DIRAbsolute path to the cloned repository in Codemagic builders
FCI_BUILD_OUTPUT_DIRContains all the artifact files that will be included in the final artifacts zip file
FCI_EXPORT_DIRAll the files included in this directory will be added to the artifacts zip file
FCI_FLUTTER_SCHEMEName of the iOS scheme to be used
FCI_SYMROOTDirectory path of files generated during Xcode build
FCI_KEYSTORE_PASSWORDPassword of Android keystore as configured in the UI
FCI_KEY_PASSWORDPassword of Android key as configured in the UI
FCI_KEY_ALIASAlias of the key as configured in the UI
FCI_KEYSTORE_PATHPath of the file in our VM