Zuplo
Bitbucket

Bitbucket 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.

YAMLbitbucket-pipelines.yml
image: node:24

pipelines:
  tags:
    v*:
      - step:
          name: Deploy Release
          script:
            - npm install
            - npx zuplo deploy --api-key "$ZUPLO_API_KEY" --environment
              "$BITBUCKET_TAG"

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