Jenkins
Jenkins is an open-source CI/CD automation server used for building, deploying, and automating software development pipelines. You can bring job and user data from Jenkins into Brinqa to gain a unified view of your CI/CD infrastructure, thus strengthening your cybersecurity posture.
This document details the information you must provide for the connector to authenticate with Jenkins and how to obtain that information from Jenkins. See create a data integration for step-by-step instructions on setting up the integration.
Required connection settings
When setting up a data integration, select Jenkins from the Connector dropdown. If you cannot find the connector in the dropdown, make sure that you have installed it first. You must provide the following information to authenticate Jenkins with Brinqa:
-
URL: The Jenkins base URL (e.g.,
https://jenkins.example.com). -
User Name: The Jenkins username used for authentication.
-
API Token: The Jenkins API token. This can be generated from Jenkins at User → Configure → API Token.
The connector authenticates using Basic Authentication. It encodes the username and API token as a Base64-encoded username:apiToken pair and includes it in the Authorization header for all API requests.
Additional settings
The Jenkins connector contains additional options for specific configuration:
- Page size: The maximum number of records to get per API request. The default setting is 100.
- Maximum retries: The maximum number of times that the integration attempts to connect to the Jenkins API before giving up and reporting a failure. The default setting is 5.
Types of data to retrieve
The Jenkins connector can retrieve the following types of data from the Jenkins API:
Table 1: Data retrieved from Jenkins
| Connector Object | Required | Maps to Data Model |
|---|---|---|
| Job | Yes | Code Repository |
| People | Yes | Person |
The Jenkins connector does not currently support operation options for the types of data it retrieves.
For detailed steps on how to view the data retrieved from Jenkins in the Brinqa Platform, see How to view your data.
Attribute mappings
Expand the sections below to view the mappings between the source and the Brinqa data model attributes.
Job
Table 2: Job attribute mappings
| Source Field Name | SDM Attribute |
|---|---|
Build.building | LAST_BUILD_BUILDING |
Build.displayName | LAST_BUILD_DISPLAY_NAME |
Build.duration | LAST_BUILD_DURATION |
Build.timestamp | LAST_BUILD_TIMESTAMP |
config.xml → definition | DEFINITION |
config.xml → jdk | JDK |
config.xml → keepDependencies | KEEP_DEPENDENCIES |
config.xml → scm → branches → name | SCM_BRANCHES |
config.xml → scm → userRemoteConfigs → url | SCM_URL |
config.xml → triggers | TRIGGERS |
config.xml root attribute | PLUGIN |
| Generated (set to "Application") | CATEGORIES |
| Generated (derived from job color) | STATUS |
| Generated (sync capture timestamp) | LAST_CAPTURED |
JobResource.className | CLASS_NAME |
JobResource.color | COLOR |
JobResource.url | UID |
JobResource.url | URL |
JobStatusResource.buildable | BUILDABLE |
JobStatusResource.concurrentBuild | CONCURRENT_BUILD |
JobStatusResource.description | DESCRIPTION |
JobStatusResource.disabled | DISABLED |
JobStatusResource.displayName | DISPLAY_NAME |
JobStatusResource.fullDisplayName | FULL_DISPLAY_NAME |
JobStatusResource.fullName | NAME |
JobStatusResource.healthReport[0].description | HEALTH_DESCRIPTION |
JobStatusResource.healthReport[0].score | HEALTH_SCORE |
JobStatusResource.inQueue | IN_QUEUE |
JobStatusResource.lastBuild.number | LAST_BUILD_NUMBER |
JobStatusResource.lastBuild.result | LAST_BUILD_RESULT |
JobStatusResource.lastBuild.url | LAST_BUILD_URL |
JobStatusResource.lastCompletedBuild.number | LAST_COMPLETED_BUILD_NUMBER |
JobStatusResource.lastFailedBuild.number | LAST_FAILED_BUILD_NUMBER |
JobStatusResource.lastStableBuild.number | LAST_STABLE_BUILD_NUMBER |
JobStatusResource.lastSuccessfulBuild.number | LAST_SUCCESSFUL_BUILD_NUMBER |
JobStatusResource.lastUnstableBuild.number | LAST_UNSTABLE_BUILD_NUMBER |
JobStatusResource.lastUnsuccessfulBuild.number | LAST_UNSUCCESSFUL_BUILD_NUMBER |
JobStatusResource.nextBuildNumber | NEXT_BUILD_NUMBER |
People
Table 3: People attribute mappings
| Source Field Name | SDM Attribute |
|---|---|
| Generated (set to "Identity") | CATEGORIES |
| Generated (set to "active") | STATUS |
| Generated (sync capture timestamp) | LAST_CAPTURED |
PeopleResource.lastChange | LAST_CHANGE |
PeopleResource.project | PROJECT |
PeopleResource.user.absoluteUrl | URL |
PeopleResource.user.fullName | NAME |
PeopleResource.user.fullName | UID |
APIs
The Jenkins connector uses the Jenkins Remote Access API. Specifically, it uses the following endpoints:
Table 4: Jenkins API endpoints
| Connector Object | API Endpoint |
|---|---|
| Job | GET /api/json |
GET /job/{name}/api/json | |
GET /job/{name}/config.xml | |
| People | GET /asynchPeople/api/json |
Changelog
The Jenkins connector has undergone the following changes:
Table 5: Jenkins connector changelog
| Version | Description | Date Published |
|---|---|---|
| 3.0.1 | Initial Integration+ release. | May 4th, 2026 |