We have recently installed the Jenkins plugin for JIRA to pull CIBuild info on the JIRA issue.
Background on Jenkins:
Jenkins home page: https://jenkins-green.clouddqt.capitalone.com/ (image 1)
The test job has been created in the folder, its 5 sub-folders in (image 2): https://sharedtechjenkins-green.clouddqt.capitalone.com/job/Non-PAR/job/Non-Prod-Jobs/job/DT_Tools_Pipeline/job/Synapse-Testing-jobs/
Jenkins home page -> Shared Tech -> NonPar -> NonProdJobs -> DT Tools Pipeline -> Synapse Testing jobs - > (job name: DeliveryServicingTest)
The integration was done under Manage Jenkins Site on the Jenkins Configuration page. (image 3)
The integration was done by adding site using the "Add Site" option (image 4)
the first integration (Jenkins-All) was done with using the (RPC url https://jenkins-green.clouddqt.capitalone.com/) of the home page. This integration did not show the number of jobs, it simply showed all the folders that are on the same Jenkins home page. (image 5).
The second integration (DSTest) was done by adding the (RPC URL https://sharedtechjenkins-green.clouddqt.capitalone.com/job/Non-PAR/job/Non-Prod-Jobs/job/DT_Tools_Pipeline/job/Synapse-Testing-jobs/) of the last sub-folder where the test job is placed. This integration showed 18 jobs that are in that sub-folder. (image 6/image 5)
The third integration was done with not the main home page but the second page of one of the folders. (image 7): (RPC URL https://sharedtechjenkins-green.clouddqt.capitalone.com/ ) This integration shows all the jobs that are in each of the folders and its sub-folders. It shows over 1000 jobs including the test job that was created in one of the sub folders
JIRA issue ID was placed in the description of the test job. This is so that the JIRA issue shows the build status when a new build was committed on that job.
scenario 1: Integration of Jenkins home page (RPC URL- RPC url https://jenkins-green.clouddqt.capitalone.com/) - FAILED
scenario 2: Integration of the last sub-folder which showed 18 jobs including the test job where the builds were commited (RPC URL used https://sharedtechjenkins-green.clouddqt.capitalone.com/job/Non-PAR/job/Non-Prod-Jobs/job/DT_Tools_Pipeline/job/Synapse-Testing-jobs/) - *FAILED*
scenario 3: Lastly the integration done using (RPC URL https://sharedtechjenkins-green.clouddqt.capitalone.com/ ) - *PASSED* When the build was committed on the test job, the JIRA issue entered in the job description was synced successfully and it displayed all the CIbuild info (image 8). This is the expected result.
Issue: Although we got it to work the issue is that the RPC url being used for the passed scenario displays over 1000 jobs that are in all the folders/sub-folders. The issue here is that we have a very large organization and pulling all the jobs is not ideal because not all jobs are to be synced with JIRA issues. The best option we see is to integrate the specific sub-folder and using that RPC URL to only bring in jobs in that one folder. This works in terms of the Jenkins integration pulling the jobs but it fails to sync with JIRA issue. Basically we would like to use the RPC URL described in scenario 2 above to successfully show the CIbuilds in JIRA.
Let me know if you have any other questions or need clarification.