Administering Keen
Jenkins
Chapter 9 of 30
Jenkins
Jenkins builds become events with the job's kind as the action and its label as the system, so build results can prove that deployments, tests or scans ran.
| Setting | Purpose |
|---|---|
KEEN_JENKINS_ENABLED | Turns the adapter on. |
KEEN_JENKINS_BASE_URL | The Jenkins server. |
JENKINS_USERNAME, JENKINS_API_TOKEN | An account that can read the jobs. |
Add a jobs collection with the job's stable name, label and kind. The adapter constructs /job/<name>/api/json for simple top-level jobs and examines up to 50 recent builds per run, so schedule collection frequently enough for the job's build rate.
The payload contains job, build, label and kind. build → result exposes the upstream result, while the event's outcome contains Keen's normalised result.
Match the values Keen records. A condition looking for deploy will not match an event whose action is deployment; inspect the actual evidence and use the exact values on the collected event.
Inspect and map evidence
Inspect a collected event and use Create mapping from this event. Structured selectors expose the payload that this source actually returns; a useful starting path is build → result. Action and outcome filters use Keen's normalised event values. Preview matching and non-matching examples.
For file-managed deployments, collection inputs live in config/jenkins.yml. See the common collection workflow for UI configuration and override behaviour.