All Integrations
CI/CDwebhook + tigerops-notify pipe

Bitbucket Pipelines Integration

Build and deployment event tracking with error correlation for Bitbucket workflows. Monitor pipeline health, track DORA metrics, and correlate every deployment with production performance.

Setup

How It Works

01

Configure the Bitbucket Webhook

Add a TigerOps webhook to your Bitbucket workspace or repository. Select the Pipeline, Build Status, and Deployment events to forward. No code changes are required in your pipelines.

02

Add the Pipe to Your Pipeline

Optionally add the tigerops/tigerops-notify pipe to your bitbucket-pipelines.yml for enriched step-level telemetry. The pipe sends test results, artifact sizes, and custom metrics alongside standard events.

03

Map Deployments to Environments

TigerOps reads Bitbucket deployment environments (test, staging, production) and automatically scopes change events to the correct environment metrics for accurate correlation.

04

Correlate Builds with Production Metrics

Every successful deployment fires a change event that TigerOps overlays on your APM and infrastructure dashboards, automatically flagging metric anomalies that follow a deployment.

Capabilities

What You Get Out of the Box

Pipeline Duration Tracking

Monitor total pipeline duration and per-step execution times across all branches and repositories. TigerOps tracks trends and alerts when pipeline times regress beyond your configured baseline.

Build Failure Error Correlation

Capture failed step exit codes, error log snippets, and affected commit SHAs. TigerOps groups failures by step name and branch pattern to surface systemic issues across your repositories.

Deployment Frequency Metrics

Track deployment frequency per environment and repository. TigerOps computes DORA deployment frequency and change lead time metrics automatically from your Bitbucket deployment events.

Change Failure Rate Monitoring

Correlate deployments with post-deploy error rate spikes, latency regressions, and on-call alerts to compute your DORA change failure rate and mean time to restore across all services.

Runner & Concurrency Metrics

Monitor Bitbucket-hosted runner concurrency, pipeline queue wait times, and build minute consumption. Alert when queue depth indicates capacity limits are being reached.

PR Build Status Insights

Track build pass rates per PR author, branch, and target. TigerOps surfaces which branches have the highest failure rates and which steps are most frequently causing build breaks.

Configuration

bitbucket-pipelines.yml with TigerOps

Add the TigerOps notify pipe to your pipeline for enriched step-level telemetry and deployment events.

bitbucket-pipelines.yml
# bitbucket-pipelines.yml — TigerOps integration
# Add TIGEROPS_API_KEY to your Bitbucket repository variables

image: node:20

definitions:
  steps:
    - step: &notify-tigerops
        name: Notify TigerOps
        script:
          - pipe: tigerops/tigerops-notify:1.x
            variables:
              TIGEROPS_API_KEY: $TIGEROPS_API_KEY
              ENVIRONMENT:      $BITBUCKET_DEPLOYMENT_ENVIRONMENT
              SERVICE:          my-api
              NOTIFY_ON_FAIL:   "true"

pipelines:
  branches:
    main:
      - step:
          name: Build & Test
          script:
            - npm ci
            - npm test
          after-script:
            - pipe: tigerops/tigerops-notify:1.x
              variables:
                TIGEROPS_API_KEY: $TIGEROPS_API_KEY
                EVENT_TYPE:       build
                SERVICE:          my-api

      - step:
          name: Deploy to Production
          deployment: production
          script:
            - npm run deploy
          after-script:
            - pipe: tigerops/tigerops-notify:1.x
              variables:
                TIGEROPS_API_KEY: $TIGEROPS_API_KEY
                EVENT_TYPE:       deployment
                ENVIRONMENT:      production
                SERVICE:          my-api
FAQ

Common Questions

Does TigerOps require access to my Bitbucket source code?

No. TigerOps uses Bitbucket webhooks and optionally the Bitbucket REST API for pipeline metadata. It never accesses your repository source code. The tigerops/tigerops-notify pipe runs inside your pipeline and only transmits metrics you explicitly configure.

Which Bitbucket plan is required for the integration?

The webhook-based integration works with all Bitbucket Cloud plans including Free. The Deployments environment mapping feature requires the Standard plan or higher, as Bitbucket Pipelines Deployments is a paid feature.

How does TigerOps compute DORA metrics from Bitbucket?

TigerOps uses deployment events for deployment frequency and change lead time. It correlates deployment timestamps with incident and alert events from your monitoring integrations to compute change failure rate and MTTR automatically.

Can TigerOps monitor self-hosted Bitbucket Data Center?

Yes. TigerOps supports Bitbucket Data Center via outbound webhooks. Configure your Data Center instance to forward pipeline and repository events to your TigerOps webhook endpoint. No inbound network access to your Data Center is required.

How long does it take to set up the Bitbucket Pipelines integration?

The webhook integration takes under 5 minutes — navigate to Repository or Workspace settings, add the TigerOps webhook URL, select your event types, and you will see pipeline events flowing into TigerOps immediately after your next build.

Get Started

Connect Deployments to Production Reality

DORA metrics, pipeline health monitoring, and deployment-to-incident correlation. Set up in under 5 minutes.