[BUG]: Azure devops pipeline does not pass variables to stages

[scholtz]

New issue checklist

• I searched for existing GitHub issues
• I read pipeline troubleshooting guide
• I checked how to collect logs

Task name

No response

Task version

No response

Issue Description

We want to create variable in the build stage and use the variable in all deployment stages.

We are able to create variable in the first stage, and pass it to the dev environment. But we are not able to pass the variable from either build stage to the 3rd stage (test) nor from the deployment to dev stage to deployment to test stage.

Environment type (Please select at least one enviroment where you face this issue)

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

ubuntu

Relevant log output

2024-11-25T17:19:36.8830621Z echo "Received variable from Dev: "

Full task logs with system.debug enabled

[build-variable.txt](https://github.com/user-attachments/files/17906739/build-variable.txt)
[deploy-to-dev.txt](https://github.com/user-attachments/files/17906740/deploy-to-dev.txt)
[deploy-to-test.txt](https://github.com/user-attachments/files/17906741/deploy-to-test.txt)
  

Repro steps

trigger:
- none

stages:
- stage: Build
  displayName: Build Stage
  jobs:
  - job: BuildJob
    displayName: Build Job
    steps:
    - script: |
        echo "##vso[task.setvariable variable=myVar;isOutput=true]Hello from Build"
      name: OutputStep

- stage: DeployDev
  displayName: Deploy Dev Stage
  dependsOn: Build
  variables:
    myVarFromBuild: $[ stageDependencies.Build.BuildJob.outputs['OutputStep.myVar'] ]
  jobs:
  - deployment: DeployJob
    displayName: Deploy to Dev
    environment: "Dev"
    strategy:
      runOnce:
        deploy:
          steps:
          - script: |
              echo "Received variable from Build: $(myVarFromBuild)"
              echo "##vso[task.setvariable variable=myVarDev;isOutput=true]$(myVarFromBuild)"
            name: SetOutputForDev

- stage: DeployTest
  displayName: Deploy Test Stage
  dependsOn: DeployDev
  variables:
    myVarFromDev: $[ stageDependencies.DeployDev.DeployJob.outputs['SetOutputForDev.myVarDev'] ]
  jobs:
  - deployment: DeployJob
    displayName: Deploy to Test
    environment: "Test"
    strategy:
      runOnce:
        deploy:
          steps:
          - script: |
              echo "Received variable from Dev: $(myVarFromDev)"

[scholtz]

Is there any timeline to fix this bug?

[hrnjan]

We are also experiencing the same issue described here by @scholtz

[scholtz]

@ericsciple @davidstaheli @DmitriiBobreshev Is there some way how to work with this? My goal is to build applications using build pipelines, and then deploy 10 applications at once to the test environment. When they are properly tested they should be deployed to prod environment. However this does not work as in the prod environment we dont have proper build info if something else was built meanwhile.. This seems to be so basic functionality that either we are missing some basic config or the azure pipelines has serious critical bug.

Btw we can solve this using the release pipelines, however there is bad management of the source of the pipes and we would like to prefer to use the build pipelines as it seems to be the future.