Skip to content

How to release extension

Jump to bottom
Vladyslav Horbachov edited this page May 28, 2024 · 1 revision

This guide provides detailed instructions on how to trigger the automated build and release pipeline for updating and deploying Azure DevOps extensions through GitHub tags. The process involves creating a new release with a specific tag that includes the extension name and version.

Prerequisites

Write access to the repository is required! Make sure that you have permissions to create a new release.

Overview of the Process

The pipeline is designed to trigger automatically when a new tag is added to the repository.

The tag should follow a specific format that includes the extension name and version number.

Tagging Format

There is a separate workflow for each extension with a dedicated trigger.

Pipeline for IIS Web App extension has the next trigger:

on:
  push:
    tags:
      - 'iiswebapp-*'

To trigger the pipeline, the tag should be formatted as follows: <extension-name>-<version>

For example, for the IIS Web App extension version 1.7.0, the tag would be: iiswebapp-1.7.0

Step-by-Step Guide to Create a New Release

  1. Go to the Releases section
  2. Draft a New Release
  3. Set the Tag and Target Branch
  • Tag version: Enter the tag according to the specified format, e.g., iiswebapp-1.7.0
  • Target branch: Ensure it is set to master. Releases from other branches are allowed only for hotfix.
  1. Provide a clear title and description
  2. Publish the Release

Please, use this release as an example: https://github.com/microsoft/azure-pipelines-extensions/releases/tag/iiswebapp-1.7.0

Clone this wiki locally