How can you use environment variables in an Azure Powershell task in a DevOps Release Pipeline?

Question

In an Azure DevOps release pipeline, I have an Agent job. Within that Agent job, I have an Azure Powershell task. I do not see a way to specify environment variables for the Azure Powershell script that the Azure Powershell task runs.

You can do it in a build pipeline by simply specifying "env" for the Azure PowerShell task:

- task: AzurePowerShell@5
  inputs:
    azureSubscription: '...'
    ScriptType: 'FilePath'
    ScriptPath: '...'
    ScriptArguments: '...'
    FailOnStandardError: true
    azurePowerShellVersion: 'LatestVersion'
  env:
    USERNAME: $(username)
    PASSWORD: $(password)

But I don't see any way of specifying "env" in a release pipeline:

How can this be done?

Not get your response for several days, would you please share your latest information about this issue? If you have any concern, feel free to share it here. — Hugh Lin
– Hugh Lin, Commented Jul 15, 2020 at 7:45
@HughLin-MSFT Sorry for the delayed response. I just responded to your answer below. — user1172282
– user1172282, Commented Jul 28, 2020 at 16:25

Hugh Lin · Accepted Answer · 2020-07-31 10:20:12Z

1

When a pipeline executes, Azure will place all pipeline variables into environment variables, so any tools, scripts, tasks, or processes you run as part of the build can access parameters through the environment.

Defining variable in the DevOps pipeline GUI:

To get the secret variable in azure powershell task, just use the syntax of $(varibaleName) to work.

edited Jul 31, 2020 at 10:20

answered Jul 10, 2020 at 10:01

Hugh Lin

19.7k3 gold badges30 silver badges33 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

user1172282 Over a year ago

This doesn't appear to be working for me. I have a secret pipeline variable named SERVERPASSWORD set to Release scope. I tried the following tests and each time SERVERPASSWORD was null: (1) Script file referencing $env:SERVERPASSWORD (2) Script file referencing $SERVERPASSWORD (3) Inline script referencing $env:SERVERPASSWORD (4) Inline script referencing $SERVERPASSWORD

user1172282 Over a year ago

I added a powershell task that runs "Get-ChildItem -Path Env:\" and I do not see my secret variables from the linked variable group or my pipeline variables. Non-secret variables do appear however.

Hugh Lin Over a year ago

I tested the syntax of $(varibaleName) , it works well .

Hugh Lin Over a year ago

@user1172282 It seems that this kind of issue has been solved, you could also consider to accept this answer. Have a nice day. :)

Hugh Lin Over a year ago

This question is related to this similar ticket.

|

Dean White · Accepted Answer · 2020-07-09 22:04:31Z

-1

What I have done with variables in a powershell script in a release pipeline is use the variable Tab where you can either add the variable pair in the pipeline variables or create a variable group in the library section and then link it.

So if you create a variable pair for say compname computer1 then in the actual powershell script reference the variable as get-azvm -name $env:compname

This will then pull the variable you have added

answered Jul 9, 2020 at 22:04

Dean White

1

Collectives™ on Stack Overflow

How can you use environment variables in an Azure Powershell task in a DevOps Release Pipeline?

2 Answers 2

6 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

6 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related