How to add secret variable as task environment variable in VSTS

user_161735 0
Viewed 7610

This documentation states that secret variables are

Not decrypted into environment variables. So scripts and programs run by your build steps are not given access by default.

One of my build tasks require that an environment variable be set that is stored in a secret variable. Does this mean it's impossible to do this using secret varaibles in VSTS? If not, how do I do this?

For further background, I'm trying to code sign my electron app using electron-builder. It requires that two environment variables be set: CSC_LINK and CSC_KEY_PASSWORD. One of these is the password to a code signing certificate so needs to be kept secure.

azure-pipelines-build-task azure-devops
3 Answers

Set Environment Variable

Use a Command Line task, like this:

VSTS Build - copy secret var to environment var

target_environment_variable now contains the value of secret_variable.

Verify

Add a subsequent Command Line task that writes all environment variables to a disk file, like this: (note: in the Arguments text box, write to a folder that both you and build agent can access):

VSTS Build - write env vars to disk


Queue the build definition, then view the file containing the environment variables:

VSTS Build - view file of env vars

user_16339490

When using the YAML-syntax this can be achieved too:

steps:
- script: |
    echo %MYSECRET%
  env:
    MySecret: $(Secret_Variable)
yoursort_804800
Related