Azure Devops Pipeline - Variable file based on branch

Question

Is it possible to have different variable template files that would be used based on the branch being built? I was trying to do something like this:

jobs:
- job: BuildandPublish
  variables:
    - template: /env/$(Build.SourceBranchName).vars.yml

But that doesn't work, I'm guessing do to the order that those variables are replaced.

Kevin Lu · Accepted Answer · 2023-01-18 02:09:15Z

1

Is it possible to have different variable template files that would be used based on the branch being built?

From your YAML sample, you are using the format: $(Build.SourceBranchName). The variable value will be expanded at runtime.

But the template will read the variable at Compile time.

To solve this issue, you need to change the format : ${{ variables['Build.SourceBranchName'] }}

Here is an example:

jobs:
- job: BuildandPublish
  variables:
    - template: /env/${{ variables['Build.SourceBranchName'] }}.vars.yml

answered Jan 18, 2023 at 2:09

Kevin Lu

36.9k4 gold badges36 silver badges50 bronze badges

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

2 Comments

MadSkeletor Over a year ago

Thanks. I had tried similar syntax based on learn.microsoft.com/en-us/azure/devops/pipelines/process/… but it didn't work. I had tried ${{ variables.Build.SourceBranchName }}

Vinod kumar G Over a year ago

we can also use the standard naming process in the environment variable and link to pipeline and use it to replace step using Build.SourceBranchName , ex - dev-tokenname, uat-tokenname

Collectives™ on Stack Overflow

Azure Devops Pipeline - Variable file based on branch

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related