Artifacts Tagger

• Overview
• Features
• Prerequisites
• How To Use
• Support

Overview

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

Features

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) or System.StageName (YAML) pipeline variable)
• Add current release name tag (use Release.ReleaseName (classic) or Build.BuildNumber (YAML) variable)
• Add user-defined tags
• Remove old runs duplicated tags

Prerequisites

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:

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.

How To Use

1. Add Artifacts Tagger task to your release pipeline
2. Select Integrated Endpoint or Service Endpoint endpoint type
3. 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.

Support

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.