How to pass powershell script variable values to downstream task in Release pipeline

Question

Created a CD with few steps starting from "Azure PowerShell Task".

In Azure PowerShell tasks, executing a PowerShell script file and set a value in a variable. At the end of the script I have set the variable with a value –

echo "##vso[task.setvariable variable=myvariable;isSecret=false;isOutput=true;]myvalue"

myvariable is the variable

myvalue is the value.

Based on the value of “myvariable”; downstream task will be executed or skipped. Mentioned "Custom Condition" in downstream task (Task - Azure Create or Update Resource) –

and(succeeded(), eq(variables[‘myvariable’], ‘myvalue’))

But, it’s always skipping the step; despite the correct value is passing. Here is my release tasks snippet -

How do I overcome?

Can you verify one step after the Azure PowerShell task that the myvariable get the myvalue? (add another task and print the myvariable value) — Shayki Abramczyk
– Shayki Abramczyk, Commented Nov 5, 2018 at 13:00
Created one powershell task and printing the value of $(myvariable). Showing error - The term 'myvariable' is not recognized. Tried to print Write-Host $myvariable, no values is printing. — Debasis Ghosh
– Debasis Ghosh, Commented Nov 5, 2018 at 13:08
i think with powershell you should use $env:myvariable. also try your condition like so: $(myvariable), myvalue. also, worth nothing, you are probably trying to do something you are not supposed to do with this approach — 4c74356b41
– 4c74356b41, Commented Nov 5, 2018 at 13:22

Alex KeySmith · Accepted Answer · 2018-11-05 15:41:35Z

2

try

Write-Host "##vso[task.setvariable variable=myvariable;isSecret=false;isOutput=true;]myvalue"

And then

and(succeeded(), eq(variables['myvariable'], 'myvalue'))

In the second part, the code you pasted in has the incorrect quote types, you had curly quotes ‘ ’ rather than the normal straight quotes ' '

You often end up with the wrong quotes if copying / pasting from Word or Outlook. I'm sure there's a proper a typography term for them.

answered Nov 5, 2018 at 15:41

Alex KeySmith

17.2k11 gold badges83 silver badges160 bronze badges

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

Comments

Debasis Ghosh · Accepted Answer · 2018-11-06 09:10:54Z

1

Thanks everyone for your valuable input. Resolution - PowerShell Script -

$myvalue="hello"
Write-Host "##vso[task.setvariable variable=myvariable]$myvalue"

Assign value ("hello") in a variable ($myvalue), then set it in "Write-Host". Direct value did not work for me. Now we can use/verify "myvariable" value in downstream tasks in Custom Condition as mentioned by @Alex KeySmith.

and(succeeded(), eq(variables['myvariable'], 'hello'))

task -

Works in Build and Release pipeline.

answered Nov 6, 2018 at 9:10

Debasis Ghosh

2634 silver badges24 bronze badges

Collectives™ on Stack Overflow

How to pass powershell script variable values to downstream task in Release pipeline

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related