Skip to main content


Visualize Jenkins entities and relationship within JupiterOne to proactively identify changes to users, jobs and repositories.


Configuration in Jenkins

To install this integration, you will need to configure settings both within Jenkins and on JupiterOne. Before enabling in JupiterOne, ensure that you complete the setup within your Jenkins's instance.

  • Install Jenkins on the local machine/server and take note of the provided domain
  • Install recommended plugins
  • Create an admin account on this installation
  • Go to Dashboard -> Configure and add a new API Token
  • Go to Dashboard -> Configure -> Manage Plugins and add the Docker and Docker Pipeline plugins
  • To push data from your Jenkins instance you must run our Docker container in a pipeline. Here is an example:
pipeline {
agent {
docker { image 'jupiterone/graph-jenkins:<version>' }

environment {
JUPITERONE_API_KEY = credentials('j1-api-key')
JUPITERONE_ACCOUNT = credentials('j1-account')
USER_NAME = credentials('jenkins-username')
API_KEY = credentials('jenkins-api-key')
HOST_NAME = 'https://<your_hostname>'

stages {
stage('Collect data') {
steps {
sh 'cd /opt/jupiterone/integration && ./scripts/'

Finalize in JupiterOne

To install the Jenkins integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Jenkins. Click New Instance to begin configuring the integration.

Creating an integration instance requires the following:

  • The Account Name used to identify the AirWatch account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • Enter the Jenkins API Key generated for use by JupiterOne.

Click Create once all values are provided to finalize the integration.

Next steps

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.