CI/CDwebhook + Travis CI API

Travis CI Integration

Build duration, job queue times, and deployment event ingestion for Travis CI. Understand your build performance trends and correlate every Travis deployment with production health.

Connect Travis CI Book a Demo

Setup

How It Works

Add TigerOps Webhook Notification

Add a TigerOps webhook URL to the notifications section of your .travis.yml. Travis CI will POST build result payloads to TigerOps on every build completion, including job-level results and timing.

Configure the Travis CI API Poller

Provide a Travis CI API token to TigerOps. The API poller supplements webhooks with richer job-level data including queue wait times, virtual machine provisioning durations, and job dependency information.

Add the Deployment Notification Script

Add the tigerops-notify script to your deploy section in .travis.yml to emit a structured deployment event with service name, environment, and Git SHA when Travis pushes a deployment.

Correlate Deployments with Metrics

TigerOps overlays Travis deployment events on your service dashboards, automatically scanning for metric regressions within your configured post-deploy correlation window and surfacing the most likely causes.

Capabilities

What You Get Out of the Box

Build Duration Trend Analysis

Track total build duration and per-job timing across all repositories and branches. TigerOps alerts when build times regress, identifies which jobs contribute most to duration, and compares trends across branches.

Job Queue Wait Time Monitoring

Monitor how long jobs wait for a Travis CI virtual machine or container before starting. TigerOps alerts when queue times consistently exceed thresholds that indicate concurrency plan limits are being hit.

Build Success Rate Tracking

Track build pass rates, failure rates, and error rates per repository, branch, and job. TigerOps computes rolling success rate trends and alerts on sustained drops that indicate infrastructure or test instability.

Deployment Event Ingestion

Capture Travis CI deploy provider events — Heroku, S3, Google App Engine, AWS Elastic Beanstalk — as structured change events. TigerOps correlates these with post-deploy metric anomalies automatically.

Concurrency & Credit Usage

Monitor Travis CI concurrent build counts against your plan limits and track credit consumption for Travis CI .com. TigerOps alerts when credit burn rate indicates you will exhaust credits before your renewal period.

Matrix Build Failure Analysis

For matrix builds, TigerOps tracks which environment matrix combinations fail most frequently — OS, language version, environment variable — helping you identify environment-specific test failures quickly.

Configuration

Travis CI Webhook & Deployment Notify

Add TigerOps webhook notifications and a deployment event script to your .travis.yml.

.travis.yml

# .travis.yml — TigerOps integration
# Set TIGEROPS_API_KEY in Travis CI repository settings (not in this file)

language: node_js
node_js:
  - "20"

cache:
  npm: true

install:
  - npm ci

script:
  - npm test

deploy:
  - provider: heroku
    app:       my-app-production
    on:
      branch:  main
    after_deploy:
      # Emit a TigerOps deployment change event after a successful deploy
      - |
        curl -s -X POST https://ingest.atatus.net/api/v1/events           -H "Authorization: Bearer $TIGEROPS_API_KEY"           -H "Content-Type: application/json"           -d "{
            "event":       "deployment",
            "service":     "my-api",
            "environment": "production",
            "version":     "$TRAVIS_COMMIT",
            "build_url":   "$TRAVIS_BUILD_WEB_URL"
          }"

# Webhook notification for all build events
notifications:
  webhooks:
    urls:
      - https://ingest.atatus.net/api/v1/travis/events?key=$TIGEROPS_API_KEY
    on_success: always
    on_failure: always
    on_start:   always

FAQ

Common Questions

Does TigerOps support both Travis CI .com and Travis CI .org?

TigerOps supports Travis CI .com. Travis CI .org has been migrated to .com since June 2021. If you are still running a legacy .org instance, contact TigerOps support for migration assistance.

How does TigerOps measure job queue wait time from Travis CI?

Travis CI webhook payloads include job queued_at and started_at timestamps. TigerOps computes the difference as queue wait time per job. The API poller retrieves this for historical jobs to build queue wait time trend charts.

Can TigerOps monitor Travis CI Enterprise (TCIE)?

Yes. Travis CI Enterprise exposes the same webhook and API interface as Travis CI .com. Configure your TCIE instance hostname in TigerOps and provide a TCIE API token scoped to read:builds and read:repos.

What deploy providers in Travis CI does TigerOps recognize as deployment events?

TigerOps recognizes deployments triggered by the Heroku, S3, GCS, Beanstalk, Heroku, Lambda, Cloud Foundry, Firebase, and script deploy providers. The deployment event includes the provider name, target environment, and Git SHA.

How do I track build performance for a monorepo with many jobs in Travis CI?

TigerOps groups Travis CI jobs by build, repository, and job name. For monorepos with many parallel jobs, TigerOps provides a job waterfall view showing the critical path and which jobs are gating overall build completion.

Get Started

Connect Travis CI Builds to Production Health

Build duration trends, queue time monitoring, and deploy-to-metric correlation. Connect Travis CI in minutes.

Start Free Talk to an Engineer