-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
-
bitbucket-branch-source-2.9.10
When a PR build starts it can be impacted by 409s (see https://issues.jenkins.io/browse/JENKINS-65718) caused by other PRs. The stacktrace shows
com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 409: [...] at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getRequest(BitbucketServerAPIClient.java:859) at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getPullRequestCanMergeById(BitbucketServerAPIClient.java:411) at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getPullRequests(BitbucketServerAPIClient.java:350) at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getPullRequests(BitbucketServerAPIClient.java:302) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:806) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:582) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:98) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:309) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE
The Bitbucket Branch Source plugin is fetching all PRs information although we are only interested in ONE of them https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/cloudbees-bitbucket-branch-source-2.9.4/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMSource.java#L806-L807. The retireval of the Jenkinsfile of a specific PR should not be impacted by other unreleated PRs. This should be improved.
- links to