APP_VERSION=$(node -pe "require('./package.json').version") echo "export APP_VERSION=$APP_VERSION" >> $HOME/.bashrc
Environment variables allow you to specify API keys, access tokens, or other secrets that your build requires, without having them checked into your repository.
Environment variables are made available during a build to any process that can use them, including custom build steps.
You can create regular environment variables which are available to all branches, or branch-specific environment variables which are only available for a specific branch.
Any environment variables set by buddybuild are available to all phases of a build.
However, environment variables set by scripts invoked by your build tool, tests, or other build-related operations, are only available while those scripts are executing.
For example, the environment variable
If you need to persist environment variables across script executions, you have a few options:
Creating default environment variables
Start by clicking on App Settings.
In the left navigation, select Build settings, then the Environment tab.
In the Environment variables row, click Configure.
Enter a name and value to create a default environment variable. Your environment variable is now ready to be consumed by your app at build time.
Create environment variables for a specific branch
You can also create environment variables for a specific branch by creating a branch-specific override.
Under Override build configuration, click Add a branch and select the branch you would like to create an environment variable for.
Select Environment variables from the dropdown and click Configure.
Enter a name and value to create your branch-specific environment variable.
Consume the variable in your build
Your environment variables will be automatically consumed by tools that are expecting them.