AldrinAJ commented on issue #8581: URL: https://github.com/apache/incubator-devlake/issues/8581#issuecomment-3319789975
Hi @dosu, Thanks for your advice above. Please be informed that there were no luck yet even after trying the below three: 1. Increased timeouts 2. Increasted retries 3. Configured scope-config based on Jenkins-Job name pattern and production pattern I am currently checking the possibilities for optimizing Jenkins server performance. **NOTE:** I would like to highlight that I could not find all the jobs (corresponds to their branches) initially after selecting the Data Scope while creating the connection. It seems all of the jobs/branches gets appearing after launching the first run. For example, Consider I have a Jenkins Multi-branch pipeline job named : `JenkinsMultiBranch` 1. While Setting Data Scope - I could see the job named : `JenkinsMultiBranch` only but I couldn't find the jobs (which is actualling inside the Job: JenkinsMultiBranch) at the list. 2. It should be like JenkinsMultiBranch/develop, JenkinsMultiBranch/feature & JenkinsMultiBranch/release 3. But after selecting the job JenkinsMultiBranch (available from the list), then creating the Data scope along with scope config (Jenkins Job pattern as JenkinsMultiBranch/*), I was able to launch the first run which would eventually fail after which I would be able to see the other jobs (JenkinsMultiBranch/develop, JenkinsMultiBranch/feature & JenkinsMultiBranch/release) from the data scope configuration. 4. After the above first run, I could see respective devlop and release jobs corresponds to their branches (only) for the Multi-branch pipeline named : `JenkinsMultiBranch`. 5. I could see other Multi-branch pipelines names **without** their respective develop and release jobs corresponds to their branches. It would appear only if we do the similar things like above. Unfortunately There were no Jenkins logs found at the jenkins machine. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
