The Artifacts Tagger extension adds a task to Azure DevOps to tag all build artifacts in a classic release pipeline or tag current run in a YAML pipeline.
| Extension | Build | Code |
|---|---|---|
 |
The Artifacts Tagger task adds various default or user-defined tags to all build artifacts in a classic release pipeline or current build in a classic build pipeline.
It uses either integrated or user-defined personal access token (PAT) Azure DevOps service endpoint to connect to projects' pipelines.
- Add current stage name tag (use
Release.EnvironmentName(classic) orSystem.StageName(YAML) pipeline variable) - Add current release name tag (use
Release.ReleaseName(classic) orBuild.BuildNumber(YAML) variable) - Add user-defined tags
- Remove old runs duplicated tags
For the task to work your release pipeline need to have a service endpoint with specific access to target project' pipelines to be able to update build tags.
There are two types of Azure DevOps service endoints supported:
| Type | Name | Account |
|---|---|---|
| integrated | SystemVssConnection | Project Collection Build Service |
| specific | User specified | User specified |
You may need to check and update build pipelines security section of Azure DevOps project allow the following access to user account of the service endpoint:
- View builds
- View build definition
- Update build information
Please refer to Azure DevOps permissions and security roles documentation for more details.
- Add Artifacts Tagger task to your release pipeline
- Select
Integrated EndpointorService Endpointendpoint type - Select default or specify custom tags to add to master build artifact
You may need to create a new Azure Pipelines service connection using PAT token.
For aditional information and support please refer to project repository. To enable debug mode to help troubleshooting issues, please configure DEBUG=artifacts-tagger:* custom release variable.
For help with Azure DevOps and release pipelines please refer to official documentation.