Azure-devops-docs: Is there a way to add git commit hash to the build name?

[jacum]

[Enter feedback here]

---

Document Details

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

• ID: a57f8545-bb15-3a71-1876-3a9ec1a59b93
• Version Independent ID: 28c87c8d-c28d-7493-0c7c-8c38b04fbcd7
• Content: Run (build) number - Azure Pipelines
• Content Source: docs/pipelines/process/run-number.md
• Product: devops
• Technology: devops-cicd-process
• GitHub Login: @juliakm
• Microsoft Alias: jukullam

[jacum]

the example goes like:
$(TeamProject)_$(Build.DefinitionName)_$(SourceBranchName)_$(Date:yyyyMMdd)$(Rev:.r)

Could we have something like
$(Date:yyyyMMdd)-$(Time:hhMMSS)-$(SourceCommitHash)
?

[jacum]

any updates on that?

[msebolt]

@jacum Apologies for the delay.

Please try using Build.SourceVersion as referenced from this post.

A similar example with $env:BUILD_SOURCEVERSION is posted here.

[jacum]

Thank you for paying attention to my question.

I tried it and it works, but in case of Git I get long hash commits, not very usable as part of BuildNumber.

This proposal
https://developercommunity.visualstudio.com/idea/1026034/add-support-substring-functions-in-azure-pipelines.html
contains solution, but it's not implemented yet... is it?

[msebolt]

You're welcome.

Thank you for providing the link, we can see if the product team will implement an easier way to handle this.

For now, directly formatting variable strings is not yet supported and the work-around is to use PowerShell, please refer to this post.

[vtbassmatt]

I'd recommend something like:

- bash: |
    HASH=$(git rev-parse --short $BUILD_SOURCEVERSION)
    echo "##vso[build.updatebuildnumber]mybuildname-$HASH"