Zuplo
Azure DevOps

Azure Pipelines: Tag-Based Releases

Applies to
Gatewayruntime for API, AI, and MCP gateways
Hosting
Managed EdgeManaged DedicatedSelf-HostedDiffers
1 difference by hosting option
Self-Hosted

Add --self-hosted-endpoint with your management API hostname to each zuplo deploy command so it targets your cluster. See zuplo deploy.

Deploy only when tags are pushed for controlled releases.

YAMLazure-pipelines.yml
trigger:
  tags:
    include:
      - v*

pool:
  vmImage: ubuntu-latest

steps:
  - task: NodeTool@0
    inputs:
      versionSpec: "24.x"
    displayName: "Install Node.js"

  - script: npm install
    displayName: "Install dependencies"

  - script: |
      TAG_NAME=$(echo $(Build.SourceBranch) | sed 's|refs/tags/||')
      npx zuplo deploy --api-key $(ZUPLO_API_KEY) --environment "$TAG_NAME"
    displayName: "Deploy with tag name"

This pipeline triggers only on tags matching v* (like v1.0.0) and creates an environment named after the tag.

Next Steps

Last modified on
Local testing in CIMulti-Stage Deployment