Jenkins alerts, routed to the right on-call engineer
Page on failed Jenkins builds with the Notification plugin, or from a pipeline's post block with curl. A green build of the same job resolves it. EvoHub turns each Jenkins alert into an on-call alert, runs it through your escalation policy, and pages people by voice call, mobile push and email.
How the Jenkins integration works
- Create a Jenkins integration in EvoHub On-Call and pick the escalation policy it should notify.
- EvoHub gives the integration its own URL (or inbound address) with a unique key — paste it into Jenkins using the steps below.
- Each Jenkins alert opens an EvoHub alert, and your escalation policy pages the on-call person — then the next step if nobody acknowledges.
- Resolves automatically when the same job and branch builds successfully again.
Set up Jenkins
Create the integration in EvoHub first — it shows your personal integration URL to paste below.
# Option A — Notification plugin (no pipeline changes)
# 1. Manage Jenkins → Plugins → install "Notification"
# 2. Job → Configure → Job Notifications → Add Endpoint
Format: JSON
Protocol: HTTP
Event: Job Completed
# Not "Job Failed and First Success": after an UNSTABLE build
# it never sends the green one, so the alert stays open.
# Avoid "All Events" too: it sends every build twice.
URL: <your EvoHub integration URL>
# With a signing secret, put it in the URL as a password —
# https://evohub:<signing secret>@ then the rest of the URL
# (the plugin cannot send headers; a generated secret needs
# no escaping).
# Option B — curl from a Jenkinsfile (any CI agent with curl)
# Store the URL as EVOHUB_URL and the signing secret as
# EVOHUB_SECRET (Jenkins credentials), then:
post {
failure { sh '''curl -fsS -X POST "$EVOHUB_URL" -H 'Content-Type: application/json' -H "X-EvoHub-Token: $EVOHUB_SECRET" -d "{\\"name\\":\\"$JOB_NAME\\",\\"build\\":{\\"number\\":$BUILD_NUMBER,\\"status\\":\\"FAILURE\\",\\"full_url\\":\\"$BUILD_URL\\",\\"scm\\":{\\"branch\\":\\"$BRANCH_NAME\\"}}}"''' }
fixed { sh '''curl -fsS -X POST "$EVOHUB_URL" -H 'Content-Type: application/json' -H "X-EvoHub-Token: $EVOHUB_SECRET" -d "{\\"name\\":\\"$JOB_NAME\\",\\"build\\":{\\"number\\":$BUILD_NUMBER,\\"status\\":\\"SUCCESS\\",\\"full_url\\":\\"$BUILD_URL\\",\\"scm\\":{\\"branch\\":\\"$BRANCH_NAME\\"}}}"''' }
}
# One EvoHub alert per job (by its full name, folder/job) and
# branch. FAILURE → high,
# UNSTABLE → medium, SUCCESS resolves; ABORTED and
# NOT_BUILT do nothing.Jenkins + EvoHub — FAQ
How do I connect Jenkins to EvoHub?
In EvoHub, go to On-Call → Integrations, add Jenkins, and choose an escalation policy. Then configure Jenkins with the integration URL EvoHub shows you — the exact steps are on this page.
Do Jenkins alerts resolve automatically in EvoHub?
Resolves automatically when the same job and branch builds successfully again.
How is the Jenkins integration priced?
Integrations are included. EvoHub bills on usage, not per seat: an ingested alert costs 1 EvoHub token (about $0.015), push and webhook notifications are free, and every account gets 200 free tokens each month.
Start free — 200 EvoHub tokens every month. See pricing.
Last updated: · EvoHub is built and operated by EvoSync Teknoloji A.Ş.