Question on Pipeline variables

jstarbird_7831

If I have a set of pipeline variables set for a stage and then change those values in the plan during a certain task shouldn't the variable now be that value for the rest of that plan?

The value is changed in one section and then later it is used in another section. At the later point it's back to what the value is set to in the pipeline.

It is all run on the same server and same for the same deployable.
Sample code of what I'm talking about:

#general
{
    set $pipelinevar1 = somevalue;

    Log-Information value is as set here: $pipelinevar1;
}

#general
{
    Log-Information value is as set in pipeline here: $pipelinevar1;
}

Product: BuildMaster
Version: 5.6.11

Pipeline variables are considered Configuration Variables, not Runtime Variables.

When you use the Set Variable Value statement, you are creating a runtime variable in the current scope, or updating a runtime variable in the current or parent scope.

If you want your scenario to work, you would need to do this...

#create a runtime variable from $pipelinevar1, which will resolve to configuration variable
set $pipelinevar1 = $pipelinevar1;

# update runtime variable created in above scope
{
    set $pipelinevar1 = somevalue;

    Log-Information value is as set here: $pipelinevar1;
}

#general
{
    Log-Information value is as set in pipeline here: $pipelinevar1;
}