Azure-devops-docs: condition: startsWith(variables['Build.SourceBranch'], 'refs/tags/release-v') will not work

[tdi]

This condition will not work since it checks a branch name against the tag name - those will not match. The condition is good for matching branch names only. I suggest to change description to reflect it works for branch name comparison not to confuse.

If there is a way to have a condition matched on tag name, it would be nice to add that somewhere to the documentation.

condition: startsWith(variables['Build.SourceBranch'], 'refs/tags/release-v').

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 3b12d2c4-f871-1d14-0c16-91e58fb1130b
• Version Independent ID: 6b9e1d67-f303-7445-e573-830309ba49a4
• Content: GitHub Release task - Azure Pipelines
• Content Source: docs/pipelines/tasks/utility/github-release.md
• Product: devops
• Technology: devops-cicd
• GitHub Login: @DavidStaheli
• Microsoft Alias: dastahel

[Shazwazza]

Does anyone know of a way to achieve the above condition for tag names?

[tdi]

@Shazwazza you can get tag with git command and add it to a variable and then condition on this maybe?

[sitereactor]

If your build is triggered by a tag when you have ie.:

trigger:
  branches:
    include:
    - refs/heads/development
    - refs/heads/master
    - refs/tags/release-v*
    exclude:

then the ['Build.SourceBranch'] will be the name of the tag, ie.: refs/tags/release-v1

So the condition will work. I'm using it this way to only trigger a certain stage for commits, which are tagged.

[kyawza-sps]

How do you use this condition for the job if you could share the syntax? @sitereactor

Currently,

I am defininging a variable
- name: is_newtag value: $[eq(variables['Build.SourceBranch'], '$(VERSION_TAG)')]

and then using it as a condition for a certain job
condition: and(succeeded(), eq(variables['is_pr'], 'False'), eq(variables.is_main, 'True'), eq(variables.is_newtag, 'True'))

[sitereactor]

@kyawza-sps I'm not sure if this is what you are looking for, but here is a stage where I use a condition for the Source Branch

  - stage: deploy_live
    displayName: Deploy code to Live  
    condition: and(succeeded(), startsWith(variables['Build.SourceBranch'], 'refs/tags/release-'))
    variables:
      environment_name: live
      service_connection: "Live Connection"
    jobs:
      - template: deploy.yml
        parameters:
          environment_name: ${{ variables.environment_name }}
          service_connection: ${{ variables.service_connection }}

[kyawza-sps]

Thank you @sitereactor. What you shared is what I was looking for.

Our repo release start with a version numbers so (e.g 0.1.19, 0.1.20), I am not certain if I can go with startsWith or go with eq against a versionTag. Will test if that work. I also don't want to manually having to change the version number if there is a major bump so starts with 0.1 might not be ideal.

Your naming scheme fits in really well with your setup.