Pass a Pipeline Variable Between Jobs

Question

Before I start using this hack that I found from an article in 2020, I would like to ask if this is a supported feature or is there an easy solution that I have overlooked.

PROBLEM: In a single pipeline, I need to get a variable from a task running on a build machine in one location and pass that over to a task running in a job in another location. Is this even possible? See image below:

Pipeline Variable Definition

Pipeline Tasks

Answer 1

No hacks are needed; you can use “Output Variables,” which lets you define variables in one job and then use them in other jobs within the same pipeline.

Here's a quick example:

1. In the job where you want to create the variable, use this command: ##vso[task.setvariable]. For example:

jobs:
- job: JobA
  pool:
    vmImage: 'ubuntu-latest'
  steps:
  - script: |
      echo "##vso[task.setvariable variable=myOutputVar;isOutput=true]somevalue"

In this case, JobA is creating an output variable called myOutputVar and giving it the value somevalue. 2. Now, in the job where you want to use that variable, you can reference it by using this syntax: $(.).

jobs:
- job: JobB
  dependsOn: JobA
  pool:
  vmImage: 'windows-latest'
  variables:
  myVar: $[ dependencies.JobA.outputs['myOutputVar'] ]
  steps:
  - script: |
    echo $(myVar)

In this example, JobB says, "I need to run after JobA finishes because I want to use that variable it created." It grabs the value of myOutputVar using the syntax  [ dependencies.JobA.outputs['myOutputVar'] ] and assigns it to a variable called myVar. Then, you can use myVar in any of the steps in JobB. Using output variables is a legit non-hack way to pass variables between jobs in different locations within the same pipeline. no hacks required. Just make sure to use the dependsOn keyword to define the order of your jobs, so the variables are ready to go when you need them.

Answer 2

1. The script (step) where you set the variable needs a name to reference (see deployVars).
2. When you set the variable you need to use isOutput=true

- job: JobA
  pool:
    vmImage: 'ubuntu-latest'
  steps:
  - checkout: none
  - script: |
      echo "##vso[task.setvariable variable=namespace;isOutput=true]mynamespace"
      echo "##vso[task.setvariable variable=ingressHost;isOutput=true]myingressHost"
    # name defines the prefix for the variables.
    name: deployVars
  - script: |
      echo "$(deployVars.namespace)"
      echo "$(deployVars.ingressHost)"

- job: JobB
  dependsOn: JobA
  pool:
    vmImage: 'ubuntu-latest'
  variables:
    # By using the prefix "deployVars." you can use the variables in JobB like in JobA
    deployVars.namespace: $[ dependencies.JobA.outputs['deployVars.namespace'] ]
    deployVars.ingressHost: $[ dependencies.JobA.outputs['deployVars.ingressHost'] ]
  steps:
  - checkout: none
  - script: |
      echo "$(deployVars.namespace)"
      echo "$(deployVars.ingressHost)"