CI and test health —in one dashboard
BuildPulse turns your existing CI data into clear per-repo metrics on test health, build performance, and flakiness. First-class GitHub Actions and Bitbucket Pipelines support, plus a direct upload API for any other CI. No agent, no opinionated process — just the numbers.
You are already collecting the data
Engineering metrics are a view on the CI signal BuildPulse already has.
Nothing new to instrument
If BuildPulse is already receiving your test results, the metrics are already being calculated. There is no agent, no tracker, and no process change to adopt.
Pick a window
Look at the last 7, 30, or 90 days per repository, so you can tell a bad week apart from a real trend.
Act on what moved
Drill from a summary into the recent builds behind it, or into the specific flaky tests doing the most damage, without leaving the page.
CI & test trends out of the box
Pass rate, test counts, and pass/fail trends over time — calculated automatically from every workflow run.
Build duration tracking
Average build time per repo over time, so you can see exactly when and where CI starts slowing down.
Flaky-test disruption
See how much flakiness is costing you, with disruption trends and the top disruptors surfaced automatically.
Recent builds at a glance
Every recent run with its branch, conclusion, and duration — filterable by date range.
No agent to install
We work straight from your Git + CI signal. Jira is supported but not required.
Healthy by default
No leaderboards, no individual scorecards. Metrics designed to be useful to engineering leaders, not weaponized against engineers.
What you get per repository
Because BuildPulse already ingests every workflow run and every test result, these are a view on data you have, not another tool to maintain.
Common questions
Do I need to install an agent or change my process?
No. These metrics are derived from the CI data BuildPulse already ingests. If your test results are uploading, the metrics are there — there is nothing else to deploy and no workflow to adopt.
Does this track individual developers?
No, and that is deliberate. There are no leaderboards and no individual scorecards. Metrics are per repository and aimed at the health of the system, not at ranking the people working in it.
Does BuildPulse report DORA metrics?
Not today. BuildPulse focuses on CI and test health — pass rate, build duration, test volume, and flaky-test disruption. If DORA reporting matters to your team, tell us and it helps us prioritise.
How far back does the data go?
You can view 7, 30, or 90-day windows per repository. History builds from the point you connect the repo, so the longer BuildPulse has been running, the more trend you have.
Do I need Jira for this to be useful?
No. Jira is supported if you want to file and track issues from a flaky test, but every metric here comes from your CI and test data alone.
Find out where your CI actually hurts
Connect a repo and BuildPulse starts charting pass rate, build duration, and how much of both your flaky tests are eating.
Free to start · No credit card required · No agent to install