How to build Buildkite dashboards in Metabase

Buildkite is a hybrid CI/CD platform where builds run on your own agents while Buildkite orchestrates pipelines, test engineering, and build insights. Metabase is where you turn that delivery activity into shared, trustworthy dashboards. This guide covers two complementary paths: a lightweight MCP + CLI route that pulls live data with the Buildkite MCP Server and loads a CSV into Metabase with the Metabase CLI, and a durable pipeline route that syncs Buildkite history into a database so you can build dashboards anyone can read.

How do you connect Buildkite to Metabase?

Most teams combine both routes: use MCP and CLI uploads for a fast first pass, then move recurring delivery reporting to a warehouse-backed model.

What can you analyze from Buildkite data in Metabase?

Once builds and the related pipelines, jobs, test executions data are in a database, the highest-value views are:

• Build pass rate by pipeline — reliability per pipeline, with main-branch health separated from PR noise.
• Build duration trend — median and p95 wall-clock time by week, before slowness becomes normal.
• Flaky test tracking — pass-and-fail-on-the-same-commit tests from Test Engineering data.
• Agent fleet utilization — whether self-hosted agents match build demand, or builds queue at peak hours.
• Deploy pipeline health — success rate and duration for the pipelines that release to production.

Which Buildkite dashboards should you build in Metabase?

How do you use the Buildkite MCP Server with the Metabase CLI?

Pair the Buildkite MCP Server with the Metabase CLI for fast, hands-on analysis. MCP is useful for scoped lookups and summarized exports; the Metabase CLI's upload command loads CSV data into Metabase and creates a ready-to-query table and model.

Example workflow

• Ask the MCP server for the last 90 days of builds with status, duration, and queue time.
• Export the result as CSV, keeping stable IDs, projects, states, and timestamps.
• Run mb upload csv to load it into Metabase as a table and model, then build questions and dashboards on top.

Be honest about the limits

• MCP lookups are excellent for exploration, not scheduled reporting.
• A CSV upload is a snapshot; refresh it with mb upload replace or move to the pipeline for real history.
• Run-grain history with queued, started, and finished timestamps is required for duration and success-rate trends.
• mb upload csv needs an uploads database configured under Admin → Settings → Uploads.

How do you set up Buildkite MCP and the Metabase CLI?

{
  "mcpServers": {
    "buildkite": {
      "url": "https://mcp.buildkite.com/mcp"
    }
  }
}

One of the strongest vendor MCP stories in CI: hosted with OAuth, a read-only variant at https://mcp.buildkite.com/mcp/readonly (ideal for analysis), plus an official local server (buildkite/buildkite-mcp-server) if you'd rather scope a token yourself.

# Install the Metabase CLI
npm install -g @metabase/cli

# Log in (opens your browser; requires Metabase v62+)
mb auth login --url https://your-metabase.example.com

# Load a builds export — creates a table AND a model
mb upload csv --file buildkite-builds.csv --collection root

# Refresh that same table later from a new export
mb upload replace <table-id> --file buildkite-builds.csv

Can you generate a Buildkite dashboard with AI?

Yes. Use the prompt below with any assistant that can run the Buildkite MCP Server and the Metabase CLI. It works end to end: if Buildkite tables already exist in Metabase it analyzes those; otherwise it pulls scoped, summarized data over MCP, loads it with mb upload csv, then builds the dashboard and caveats any metric that needs missing history.

Create a polished Metabase dashboard for Buildkite ci/cd analytics.
Work end to end: get the data into Metabase if it isn't there yet, then build.

Goal: Help engineering leaders understand build health, pipeline performance, test quality, and delivery throughput from Buildkite data.

Step 1 — Find or load the data:
- First, check what already exists in Metabase (search for buildkite tables and
  models). If durable Buildkite data is already present — synced from a warehouse
  or uploaded earlier — use it and skip to Step 2.
- If nothing is there, pull a scoped, summarized export with the Buildkite MCP Server:
  builds, plus pipelines, jobs, test executions.
  Prefer entity tables and rollups over raw logs. Write each result to a CSV,
  then load it with the Metabase CLI — run "mb upload csv --file <export>.csv" so
  each upload creates a table and a ready-to-query model. Use "mb upload replace
  <table-id> --file <export>.csv" to refresh an existing table instead of creating
  duplicates.

Step 2 — Inspect before querying:
Do not assume exact table or column names. Inspect available fields, projects,
branches, states, and timestamps, and whether history exists before creating
duration or trend cards.

Important:
- Build on whatever data is present; don't claim Metabase connects natively to
  Buildkite — it reads a database or CLI-uploaded tables.
- Never try to load raw build logs or event streams into Metabase; use runs,
  entities, state changes, and rollups.
- Only compute durations (cycle time, build duration, time to review) when the
  required timestamps exist.
- Exclude bot activity, draft work, and non-production environments from
  headline numbers, and keep the segmenting column explicit.
- A single CSV is a point-in-time snapshot: only build trend cards if there is a
  usable date column or multiple periods have been uploaded.

Dashboard title: Buildkite CI/CD Overview

Sections:
1. Executive summary: Builds last 30 days; Success rate; Median duration;
   Flaky tests flagged; Production deploys.
2. Build health: Success rate by week; failed builds by job; builds per day.
3. Performance: Median and p95 duration by week and pipeline; queue time.
4. Test quality: Flaky tests by failure rate; test failures per week; retries.
5. Throughput: Deploys per week; change failure rate; lead time where synced.

Filters: Date range, Project or Repository, Branch or Environment, Team, Status.

Output: Build the dashboard if you have permission; otherwise provide the exact
questions, SQL, model definitions, and layout. Include caveats for any metric
that cannot be calculated from the available data.

How do you sync Buildkite data into a database or warehouse?

For dashboards that need history and reliability, land Buildkite entities and change history in a database first, then connect Metabase to that database.

Connector options

• Managed ETL — use a connector when one covers the objects you need.
• Custom pipeline — use the Buildkite REST and GraphQL APIs for control over fields, grain, and refresh cadence.
• MCP + CSV — use this for quick exploration and one-off slices.

Airbyte has a community Buildkite source for builds, pipelines, and organizations. Buildkite's APIs paginate cleanly by pipeline and build, so a scheduled script that lands builds, jobs, and Test Engineering runs is a realistic lightweight pipeline too.

Notes

• Land raw entity tables first, then build clean Metabase models on top.
• Sync state-change or audit history from day one — duration metrics can't be reconstructed later without it.
• Normalize project or job, branch, status, queued/started/finished-timestamp, and duration fields.

How should you model Buildkite data in Metabase?

Core tables

Modeling advice

• Build a clean pipeline_runs model with common columns across tools, so multi-source dashboards don't fork definitions.
• Separate entity tables (projects, repos, flags, members) from run-grain and event-grain tables.
• Exclude bots, drafts, and non-production environments from headline metrics; keep the flag as an explicit column.
• Use stable IDs for project, repo, and person joins; display names change.

Which Buildkite metrics should you track in Metabase?

What SQL powers Buildkite dashboards in Metabase?

These assume a cleaned analytical model in a warehouse (PostgreSQL dialect). Adjust table and column names to match your pipeline.

SELECT
  date_trunc('week', started_at) AS week,
  COUNT(*) AS builds,
  ROUND(
    100.0 * COUNT(*) FILTER (WHERE result = 'success')
    / NULLIF(COUNT(*), 0), 1
  ) AS success_rate_pct
FROM pipeline_runs
WHERE branch = 'main'
GROUP BY 1
ORDER BY 1;

SELECT
  pipeline_name,
  percentile_cont(0.5) WITHIN GROUP (
    ORDER BY duration_seconds
  ) / 60.0 AS median_minutes,
  percentile_cont(0.95) WITHIN GROUP (
    ORDER BY duration_seconds
  ) / 60.0 AS p95_minutes
FROM pipeline_runs
WHERE started_at >= CURRENT_DATE - INTERVAL '30 days'
  AND result = 'success'
GROUP BY pipeline_name
ORDER BY median_minutes DESC;

SELECT
  test_name,
  COUNT(*) AS runs,
  COUNT(*) FILTER (WHERE result = 'failed') AS failures,
  ROUND(
    100.0 * COUNT(*) FILTER (WHERE result = 'failed')
    / NULLIF(COUNT(*), 0), 1
  ) AS failure_rate_pct
FROM test_results
WHERE run_at >= CURRENT_DATE - INTERVAL '14 days'
GROUP BY test_name
HAVING COUNT(*) FILTER (WHERE result = 'failed') > 0
  AND COUNT(*) FILTER (WHERE result = 'passed') > 0
ORDER BY failure_rate_pct DESC
LIMIT 20;

What are common mistakes when analyzing Buildkite in Metabase?

Related

Related analytics

Related dashboards

Related integrations

FAQ