Jenkins monitoring
Jenkins monitoring alongside your modern CI
Most teams running Jenkins also run something else. Surface every job alongside your GitHub Actions, GitLab, or Bitbucket runs. DORA aggregated across both estates. API token only, no plugin install.
Repos across Jenkins (42 jobs) + GitHub Actions (18 workflows)
Works across every major CI/CD provider
Jobs · DORA · Flaky tests
Beyond the Jenkins dashboard
Three capabilities every CI/CD Watch tenant uses, each wired into how Jenkins reports data via its REST API. Jenkins jobs and modern CI runs in the same view, with cost translated to dollars from your own infra rate.
Jenkins jobs and modern CI, one feed
The Jenkins dashboard shows Jenkins. Your team ships across both.
Jenkins jobs, GitHub Actions runs, GitLab pipelines, all in one live feed. Freestyle, Pipeline, and Multibranch Pipeline jobs all tagged. Drill back to each source's native page when you need the raw logs.
- Outbound HTTPS to Jenkins via its REST API: no plugin install, no inbound network changes
- Freestyle, Pipeline, and Multibranch Pipeline jobs surfaced with a clear type tag
- Each row links straight to <jenkins-url>/job/<name>/<build>/
Outcome: one tab across the whole estate, no Jenkins/modern-CI split-brain.
What's needed: a Jenkins API token from a user with read access. Nothing on Jenkins changes.
Jenkins (42 jobs) + GitHub Actions (18 workflows) · live
DORA, across Jenkins and modern CI
Five DORA metrics, calculated across Jenkins and modern CI as one estate.
DORA metrics from Jenkins job runs and your modern CI together. Job-name patterns or pipeline stage names detect deploys (e.g. jobs matching *-deploy or Pipeline stages named Deploy). Multibranch pipelines treated correctly: each branch is its own series.
- Jenkins counted alongside every other provider, not as a separate silo
- Deploy rules target job names or Pipeline stage names (stage('Deploy'))
- Multibranch pipelines: each branch series counted independently, no cross-branch conflation
Outcome: one DORA story for the whole estate, not two.
What's needed: Jenkins API token. Auto-detection covers naming conventions; named rules take five minutes otherwise.
DORA by provider · 30 days · all jobs
Flaky tests, surfaced via the JUnit publisher
If you already publish JUnit, we surface the flakes.
The JUnit publisher plugin is ubiquitous on Jenkins. If your job already runs junit '**/*.xml' (Pipeline) or has the Publish JUnit post-build step (Freestyle), the data is there. Tests rank by flip rate and failure rate across branches.
Pipeline (Jenkinsfile)
post {
always {
junit '**/target/surefire-reports/*.xml'
}
}- Per-test flip rate scored across branches over a rolling 30-day window
- Failure rate and current status per test, sortable in the table
- Multibranch Pipeline tests merged per logical test across branches
Outcome: fix the disruptive tests first, with real flip-rate data to triage them.
What's needed: JUnit publisher plugin (already installed on most Jenkins instances).
Flaky tests, last 30 days, sorted by flip rate
Same connect, more depth
How we work with Jenkins
Three more capabilities the same connect unlocks. None of them are Jenkins-only, but each pays off particularly well on Jenkins estates where infra cost configuration, mixed-CI migration, and per-repo branching strategy all swing the picture.
Cost
Cost-optimization opportunities ranked by potential saving
Right-sizing recommendations, redundant-step detection, and waste categorisation. Uses your configured agent-hour rate (Jenkins is the only provider where you set the rate yourself).
Audit
Audit rules catch CI/CD hygiene gaps across the estate
Built-in rules check for missing lint, no unit tests, absent SAST, secrets-in-config patterns, and more. Findings ranked by severity; each one names the job and the fix.
Strategy
Branching strategy auto-detected per repo
Trunk-based, GitFlow, GitHub-flow detected from your real branch and merge patterns. DORA metrics get a per-strategy lens so trunk-based repos aren't penalised for not having long-lived release branches.
All from one connect
Plus the rest of the toolkit
The three capabilities above are what you'll use most. Same connect also gives you cost tracking, PR health, stability classification, performance ratings, security insights, Slack, CLI, and an MCP server. No extra integrations.
Cost tracking →
Per-agent-hour cost using your configured rate, plus developer wait time. Team tier.
PR health →
Per-repo CI failure rates, reviewer wait time, and PR-to-deploy latency. Team tier.
Stability classification →
Every job auto-classified healthy, flaky, or broken. Trend detection on each.
Performance ratings →
Per-job performance scoring across the estate. Spot the slow outliers.
Security insights →
Per-repo security-scan detection rolled up across the estate. Business tier.
Slack notifications →
Job failures, regressions, and degradation alerts in your team channel. Team tier.
CLI →
Query job status, costs, and DORA from your terminal. Pipe it anywhere.
MCP server →
Hook Claude, Cursor, or any AI agent into live pipeline state.
Pricing
Flat per tenant
Start free for one team. Team and Business tiers are flat monthly rates per tenant. Enterprise is custom for organisations needing SSO, audit logging, and security review.
Free
For one team getting started with up to 3 repos.
- 3 repos
- 1 team member
- Jobs, DORA, flaky tests
- Cost view (last 30 days)
- Email support
Team
Flat rate per tenant. Up to 20 repos and 10 team members.
- 20 repos
- 10 team members
- Everything in Free
- Cost tracking with full history
- PR health, performance ratings
- Slack notifications, CLI, MCP server
Business
Flat rate per tenant. Up to 100 repos and 50 team members.
- 100 repos
- 50 team members
- Everything in Team
- Audit findings and cost-optimization opportunities
- Priority support
Comparison
How CI/CD Watch compares
A 10-person team running Jenkins (likely alongside modern CI) across ~20 repos. Headline pricing only; deeper feature comparisons live on the linked pages.
CI/CD Watch$29 / mo flat (Team) | ||||
|---|---|---|---|---|
| Jenkins + modern CI in one feed | Yes, by design | Add-on | Limited | No |
| DORA aggregated across providers | Yes | Add-on | Yes | No |
| No-plugin Jenkins integration | API token only | Plugin install | Plugin install | Plugin install |
| Cost using your configured infra rate | Yes | No | No | No |
| Pricing model | Flat per tenant | Per committer + spans | Per contributor | Flat tiers |
| Setup time | ~2 min API token | Agent install per repo | OAuth + config | ~5 min |
Competitor pricing reflects each vendor's published headline rate. See the linked comparison pages for fuller feature matrices and verified sources.
~2 min
to connect via API token
0
plugins to install on Jenkins
5
DORA metrics from day one
Flat
per-tenant pricing
FAQ
Jenkins specifics
- Do we need to install a plugin on Jenkins?
- No. CI/CD Watch reads from Jenkins' built-in REST API using an API token. No plugin to install, no Groovy script to vet, no security review of a new artifact. Outbound HTTPS from us to your Jenkins instance. No inbound network changes required.
- How does CI/CD Watch get our Jenkins data?
- Standard Jenkins REST API endpoints (/api/json, /job/<name>/api/json, etc.) using the API token of a user with read access. Polling is rate-limited and conditional-request-aware so it doesn't add load.
- Does it work with Freestyle, Pipeline, and Multibranch Pipeline jobs?
- Yes, all three. Each job type is tagged so you can filter on it. Multibranch Pipeline jobs treat each branch as its own series, so DORA for the main branch isn't conflated with feature-branch builds.
- Can we see Jenkins alongside our modern CI?
- That's the main reason teams connect Jenkins. Connect Jenkins and GitHub Actions (or GitLab, Bitbucket) separately; both surface in the same feed and DORA aggregates across them. Particularly useful mid-migration when you're moving jobs off Jenkins and need to track progress.
- How is cost calculated for Jenkins (since there's no SaaS rate card)?
- You configure a per-agent-hour rate in Settings: typically your AWS/GCP/on-prem compute cost plus an estimate for ops/oncall overhead. CI/CD Watch applies that rate to the job runtime. Developer wait time is calculated the same way as on every other provider.
- How long does setup take?
- Around two minutes. Generate an API token in Jenkins for a read-only user, paste the Jenkins URL and token into CI/CD Watch, pick which jobs/folders to include. The first feed populates within minutes.
- Is pricing tied to Jenkins jobs or seats?
- Neither. CI/CD Watch is flat per tenant: $0 Free, $29 Team, $99 Business per month. Repo and team-member caps differ per tier; consumption inside those caps is unmetered.
- Cloud-hosted Jenkins via CloudBees or similar?
- Yes. CloudBees CI, AWS-hosted Jenkins, self-managed Jenkins on Kubernetes all behave the same as far as the API is concerned. As long as we can reach the Jenkins URL with the token, it works.
- What if our Jenkins is behind a VPN or only reachable internally?
- We support outbound HTTPS only, so the Jenkins instance needs to be reachable from our servers. If your Jenkins is internal-only, you'd need to expose it via a reverse proxy with token-protected access or, on Enterprise, run our connector inside your network. Get in touch.
More on CI/CD monitoring
Read, compare, or get started
Blog
What are DORA metrics and why should you track them?
The four (now five) signals from DORA Research that measure how well a software team delivers. What each one means and how to read them.
Guide
Deployment detection
Auto-detection from job-name patterns or Pipeline stage names. Configure named rules for non-default conventions.
Guide
Audit
How CI/CD Watch audits your jobs for missing tests, missing lint, and other CI/CD hygiene gaps.
Blog
Flaky tests: what they are, why they happen, how to fix them
Practical patterns for catching flaky tests early, ranking them by impact, and clearing them without halting feature work.
Blog
The true cost of CI/CD: compute, wait time, and waste
Compute is half the bill. Developer wait time is usually the bigger half. The taxonomy of CI/CD cost and where the waste lives.
Blog
CI/CD monitoring: beyond watching pipelines go green
What estate-level CI/CD monitoring should actually surface, and where most dashboards stop short.
One feed across Jenkins and modern CI.
Connect Jenkins in two minutes. Jobs, DORA, and flaky tests alongside your modern CI estate. API token only, no plugin install.