---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Onboard Jenkins using Classic

# Onboard Jenkins to DevOps Change Velocity --- Classic {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Connect your Jenkins instance to discover and track your pipelines, and import your orchestration tasks for end to end traceability and change automation.

## Before you begin

Role required: sn_devops.admin or sn_devops.tool_owner

Install and enable the ServiceNow DevOps plugin for Jenkins. If you've already installed it, update to the latest version. For instructions, see [Configure Jenkins plugin](https://www.servicenow.com/docs/mh0wc8xKI9wbIrm8Jx_0uw#configure-jenkins-plugin "Configure Jenkins to send real time notifications for your pipeline executions to DevOps Change Velocity.").

## About this task

Actions:

* Connect to Jenkins and get the webhook URL when you submit a DevOps tool record.
* Discover orchestration tasks and pipelines.
* Import task execution and step execution records.
{#create-jenkins-tool-dev-ops__ul_sjj_zch_rjb}  
Note:  
You can authenticate your connection with Jenkins using Jenkins API tokens. For more information, see [Connect to Jenkins using API token authentication](https://www.servicenow.com/docs/z_P6~CHBqTP2wOJ_AntEXQ "Connect to Jenkins using API token authentication instead of user name and password.").

## Procedure

1. Create a tool record in DevOps to automatically connect to Jenkins and get the webhook URL.
   1. Navigate to DevOpsToolsCreate New (legacy) and create a record.
   2. Enter a Tool Name and fill in the tool details.  

      |-|-|
      | Tool Integration | Jenkins |
      | Tool URL | Jenkins tool URL For example: <kbd class="ph userinput">https://jenkins.com</kbd> |
      | Tool Username | Jenkins user name |
      | Tool Password / Access Token | Jenkins password, access token or the API token you generate. Note: To generate API token, see [Connect to Jenkins using API token authentication](https://www.servicenow.com/docs/z_P6~CHBqTP2wOJ_AntEXQ "Connect to Jenkins using API token authentication instead of user name and password."). |
      [ ]

      {#create-jenkins-tool-dev-ops__table_aqb_5w1_ymb}

      For a list of all the permissions required on the credentials for connecting to Jenkins, see Jenkins permissions in [Permissions required for DevOps tools](https://www.servicenow.com/docs/rkQZOOxQSNdDZ7d5eHch0A "Permissions required in your third-party tool to connect to DevOps Change Velocity.").
   3. Select MID Server for an on-premises tool that is attached to a MID Server.  
      The Application value is automatically set to DevOps and the Capability value is set to REST.
   4. Click Submit.  
      The tool is connected successfully.
   {#create-jenkins-tool-dev-ops__substeps_v1d_4w1_ymb}

On successful tool creation, you're taken to the tool record page.

2. If you want to control access to the tool, add the groups that must be given access to the tool in the Maintained by field on the Access tab.  
   The tasks the users in the groups can perform depends on the roles assigned to them.
   * DevOps Tool Owner role: Can view and edit the tool.
   * DevOps App Owner role: Can view the tool and can associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects (such as plans, repositories, and pipelines).
   * DevOps Administrator role: Can edit all tools.
   * Other DevOps roles: Can view the tool.

   {#create-jenkins-tool-dev-ops__ul_qnp_fkx_5wb}  
   Note:  
   Only groups containing users with DevOps roles are available for selection in the Maintained by field.

   The All App Owners can view and associate tool objects to applications option becomes available for selection if you choose to restrict access to the tool. This option enables all users having the DevOps App Owner role to access the tool. If selected, they'll be able to view, associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects.
3. Click Discover to discover the existing orchestration tasks (Jenkins stages) and pipelines.  
   Note:  
   Orchestration tasks and pipelines are discovered for folders nested to the level specified in the sn_devops.discover.folder.depth property. For more information, see [Properties installed with
   DevOps](https://www.servicenow.com/docs/Cy67V7Lf9sOXU2beB3VARQ "Use these properties to configure settings in the DevOps Change Velocity application.").  
   Records are added to the corresponding related lists.
4. Open a discovered record from the Orchestration Tasks related list and click the Import related link to import historical data from the orchestration task.  
   Imported task execution records and step execution records are added to the corresponding related lists.

*[\>]: and then