Jenkins Sensor

What it ingests

CI/CD build results from Jenkins — deploys, failures, and recovery patterns. The sensor is webhook-driven: Jenkins POSTs build notifications to Corveil, so there's no outbound polling and on-prem Jenkins works through any firewall.

Credential

None to create. Unlike the polling sensors, the Jenkins sensor's webhook token is generated server-side at create time and stored internally. The plaintext token is returned once in the create response so the UI can show you the full webhook URL — copy it then; it isn't shown again.

Config fields

Both config fields are optional.

Key	Notes
`instance_label`	Human-readable name shown in the UI, e.g. `acme-prod-jenkins`. Display-only; not used for auth.
`job_allowlist`	Comma-separated job names to ingest, e.g. `deploy-prod, deploy-staging`. Applied at ingest time by the webhook handler. Blank accepts all jobs.

Wire-up

POST /api/sensors

json

{
  "sensor_type": "jenkins",
  "name": "Acme Jenkins",
  "config": {
    "instance_label": "acme-prod-jenkins",
    "job_allowlist": "deploy-prod, deploy-staging"
  }
}

The response includes the generated webhook URL + token. Save it.

Provider-side setup

Point Jenkins at the webhook URL from the create response. Use the Notification plugin (or a curl post-build step) to POST build results to that URL on job completion. Only jobs in job_allowlist are ingested if you set one.

Verify

Trigger a build (or run the allowlisted job). The build result should appear as a CI/CD event shortly after the job finishes. If nothing arrives, re-check the webhook URL/token in Jenkins and that the job name matches the allowlist.

Jenkins Sensor ​

What it ingests ​

Credential ​

Config fields ​

Wire-up ​

Provider-side setup ​

Verify ​