---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Reduce calls from Jenkins to ServiceNow DevOps to fetch pipeline information

# Reduce calls from Jenkins to ServiceNow
DevOps to fetch pipeline information {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Enable the Force Tracking Check field in the Jenkins configuration form
to create a pipeline tracking file in Jenkins. ServiceNow
DevOps makes a REST call to Jenkins to update the tracking file
when the Track field in a pipeline is modified.

## Force Tracking Check {#reduce-pipeline-info-calls-jenkins__section_u3f_pdw_mqb}

The ServiceNow DevOps configuration section in Jenkins includes a Force Tracking Check check box to reduce the number of calls made from Jenkins to DevOps to fetch pipeline information such as pipelines being tracked. Base-system flows:

* DevOps Jenkins File Update- Track flow
* DevOps Jenkins File Update- Test Info flow
{#reduce-pipeline-info-calls-jenkins__ul_anv_13w_mqb}

## How it works {#reduce-pipeline-info-calls-jenkins__section_hgg_tjw_mqb}

In previous versions, a REST call fetched the pipeline information for every Jenkins build triggered. If you had multiple pipelines in your Jenkins environment and were tracking only a few of them, this meant that a
call was made to fetch the tracking information for each pipeline even if you were tracking
a few of them.

The
first time you trigger a Jenkins build or pipeline execution, Jenkins makes a pipeline information API call and creates
<var class="keyword varname">snPipelineInfo.json</var> file in
/{JENKINS_HOME}/jobs/{jobName} directory. For each subsequent
pipeline execution Jenkins checks the information available in the
<var class="keyword varname">snPipelineInfo.json</var> file before making a pipeline info API call.  
If you disable the Force Track Check check box:

* The DevOps Jenkins File Update- Track flow triggers when you update the Track field on the pipeline form. The Track field info is updated in the <var class="keyword varname">snPipelineInfo.json</var> file.
* DevOps Jenkins File Update- Test Info flow triggers when you update Test type mapping for Jenkins tool integration and verify that Test info is updated in <var class="keyword varname">snPipelineInfo.json</var> file.
{#reduce-pipeline-info-calls-jenkins__ul_cnm_n3w_mqb}

If you enable the Force Track Check check box, Jenkins makes pipeline info API calls to DevOps even if track/test information
exists in the <var class="keyword varname">snPipelineInfo.json</var> file.