{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":32202,"path":"it-service-management/devops-change-velocity/reduce-pipeline-info-calls-jenkins.md","title":"Reduce calls from Jenkins to ServiceNow DevOps to fetch pipeline information","bundle":null,"doc_type":null,"release":"australia","body":"\n# Reduce calls from Jenkins to ServiceNow DevOps to fetch pipeline information\n\nEnable 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.\n\n## Force Tracking Check\n\nThe 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:\n\n-   DevOps Jenkins File Update- Track flow\n-   DevOps Jenkins File Update- Test Info flow\n\n## How it works\n\nIn 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, a call was made to fetch the tracking information for each pipeline even if you were tracking only a few of them.\n\nThe first time you trigger a Jenkins build or pipeline execution, Jenkins makes a pipeline information API call and creates *snPipelineInfo.json* file in `/{JENKINS_HOME}/jobs/{jobName}` directory. For each subsequent pipeline execution Jenkins checks the information available in the *snPipelineInfo.json* file before making a pipeline info API call.\n\nIf you disable the **Force Track Check** check box:\n\n-   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 *snPipelineInfo.json* file.\n-   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 *snPipelineInfo.json* file.\n\nIf you enable the **Force Track Check** check box, Jenkins makes pipeline info API calls to DevOps even if track/test information exists in the *snPipelineInfo.json* file.\n\n"}}