pipepulse

Pipeline health dashboard for GitLab™.

GITLAB is a trademark of GitLab Inc. in the United States and other countries and regions. pipepulse is an independent project, not affiliated with, endorsed, sponsored or approved by GitLab Inc.

Monitor multiple GitLab projects from a single view — with history, trends, and inline failure logs.

Live demo: pipepulse.morv.dev (generated sample data, no GitLab token needed)

---

Why

Most CI dashboards show only the current state. pipepulse stores pipeline history in Postgres and surfaces:

• Trends — is your build getting slower? fail rate rising? Compared with the previous 7/30/90 days
• MTTR — time from a failure on the default branch to the next green pipeline, with incident history
• Inline failure logs — expand a failed job's last N lines without leaving the dashboard
• Pulse — a per-project EKG-style strip of the last 20 runs: failures spike, passing runs are sized by duration

Inspired by larscom/gitlab-ci-dashboard and ci-dashboard/gitlab-ci-dashboard. pipepulse adds persistent history, trend analytics, and a premium-grade UI.

---

Stack

Layer	Tech
Backend	Python · FastAPI · async background worker
Database	PostgreSQL
Frontend	Next.js · TypeScript · Recharts
Infra	Docker · Helm (k3s) · GitHub Actions
Demo	Vercel (dashboard only, snapshot data) · pipepulse.morv.dev

---

Features (MVP)

• Track GitLab projects (gitlab.com or self-managed) with just a read_api token: every accessible project by default, or a chosen list
• Aggregate pipeline stats: runs, success rate, avg and p90 duration
• Per-project view: trend chart, fail rate, MTTR
• Inline job logs (ANSI colors, GitLab sections) under active failures and failed pipelines
• Filter and sort pipelines by status, ref (default branch or all) and source; slowest first
• Demo mode — works out of the box with generated data, no token required

---

Design

• Monospace font for data (numbers, durations, SHAs, timestamps) — sans for labels and nav
• Color carries meaning: teal = success · coral = failure · amber = running
• Dense list layout (not cards) — more dashboard, less landing page
• Signature element: pulse bar — a row of thin stripes per project, each stripe = one pipeline run
• Light/dark theme (dark by default); keyboard-accessible; prefers-reduced-motion respected

┌─────────────────────────────────────────────────────────────────┐
│  Projects: 6   Active failures: 2   Avg build: 4m 12s   ✓ 94%  │
├────────────────┬──────────────────────┬────────────┬────────────┤
│ Project        │ Pulse (last 20)      │ Status     │ Duration   │
├────────────────┼──────────────────────┼────────────┼────────────┤
│ api-service    │ ▁▃▂█▂▁▃▂▁▁▂▃▁▂█▂▁▃▂▁│ ✓ success  │ 3m 48s     │
│ web-frontend   │ ▂▁▃█▁▂▃▁▂▃▁▂▁▃▁▂▁▃▁▂│ ✗ failed   │ 6m 02s     │  ← expanded
│   └─ test:e2e  │ Error: Cannot find module './auth' ...         │
│ infra-deploy   │ ▁▁▂▁▃▁▁▂▁▃▁▁▂▁▁▃▁▁▂▁│ ✓ success  │ 1m 15s     │
└────────────────┴──────────────────────┴────────────┴────────────┘

---

Roadmap

• Project spec & architecture decisions
• Repo structure, docker-compose (api + postgres)
• GitLab API client (projects, pipelines, jobs, trace)
• Data model + migrations
• Background polling service
• API endpoints: projects, pipelines, aggregates, job log
• Seed data for demo mode
• Frontend: design tokens, dark/light theme
• Pulse component
• Summary bar + project list
• Per-project view (trend chart, fail rate, MTTR)
• Inline log viewer
• Pipeline filters, sorting, pagination
• Configuration through environment variables (token, optional project list)
• Dockerfiles + Helm chart (tested on a local k3s cluster)
• CI (GitHub Actions)
• Frontend-only demo mode (snapshot of the real API)
• Live demo on pipepulse.morv.dev
• Prometheus metrics
• Published images and Helm chart (GHCR), install tested in CI

---

Demo

The public demo is the dashboard alone, deployed on Vercel with PIPEPULSE_DEMO=true. It needs no backend or database: it serves web/src/demo/snapshot.json, a snapshot recorded from the real API on generated data (6 projects, 60 days of history). Timestamps are shifted to "now" on every request, so the demo never looks stale.

Regenerate the snapshot after changing the API or the demo data:

docker compose up -d postgres migrate
cd api && uv run python -m pipepulse.seed.snapshot ../web/src/demo/snapshot.json

To run pipepulse for real against your GitLab, deploy it on Kubernetes (next section) or use docker-compose (below).

Deploy on Kubernetes

Images (amd64, arm64) and the Helm chart are published to GHCR on every release.

your-host ─▶ Ingress ─┬─ /api/* ─▶ api (FastAPI)
                       └─ /*     ─▶ web (Next.js)
                          worker (polls GitLab) · postgres · migrate job (on every release)

A look with generated data, no GitLab token needed:

helm install pipepulse oci://ghcr.io/morveusz93/charts/pipepulse \
  -n pipepulse --create-namespace --set demo.enabled=true

Against your GitLab, with a read_api token stored in a Secret:

This is the beginning of the README. Read the rest at the original. Read the full README ↗