How to access secured repository variables in windows runner?

[Chris]

Hi!

When accessing repository variables in my windows runner pipeline via

$env:SOME_VAR 

everthing works EXCEPT when the variable is set to be "secured"! In that case the ENV is not set/empty!

How to access secured variables? Am i missing something or is this a bug?

[Mark C · Accepted solution]

Hi @Chris,

Thank you for reaching out to the community.

You can safely access secured variables by following the solutions mentioned in this knowledge-based article. - How to safely export secured variables in bitbucket pipelines

Regards,
Mark C

[Chris]

I can access all types of variables in our Linux runner, but with a Windows runner only "unsecured" aka normal variables work!

[Chris]

sorry, my bad! got it working now by additionally en-/decoding the secured values with base64

[Daan Baas]

Hi, 

We have exactly the same problem @Chris descibes. We use a Windows Self-Hosted runner, and we are trying to send a build artifact (installer package) to the Downloads section of our repository. 

We already wasted a full day on this, trying different options. To verify whether the use of 'secured' variables in combination did not cause problems with the 

$env:SOME_VAR 

 syntax in our bitbucket-pipelines.yml, we tried using un-secured variables. With unsecured variables, our scripts can read the repository variables. I tried reading the knowledge-based article. - How to safely export secured variables in bitbucket pipelines
mentioned above, but it does not exist anymore.