Skip to content

Latest commit

 

History

History
23 lines (17 loc) · 946 Bytes

label-sources.md

File metadata and controls

23 lines (17 loc) · 946 Bytes
ms.topic ms.service ms.manager ms.author author ms.date
include
azure-devops-pipelines
mijacobs
sdanie
steved0x
02/13/2020

You may want to label your source code files to enable your team to easily identify which version of each file is included in the completed build. You also have the option to specify whether the source code should be labeled for all builds or only for successful builds.

Note

You can only use this feature when the source repository in your build is a GitHub repository, or a Git or TFVC repository from your project.

In the Label format you can use user-defined and predefined variables that have a scope of "All." For example:

$(Build.DefinitionName)_$(Build.DefinitionVersion)_$(Build.BuildId)_$(Build.BuildNumber)_$(My.Variable)

The first four variables are predefined. My.Variable can be defined by you on the variables tab.