Jenkins构建Fork仓库Pull Request时找不到提交的解决方案咨询

我们使用Bitbucket Push and Pull Request插件构建项目时，源仓库的Pull Request（PR）可正常拉取代码构建，但来自Fork仓库的PR会因提交仅存在于Fork中而找不到对应提交，导致构建失败。相关代码和错误信息如下：

Jenkinsfile示例 #

pipeline {

  triggers {
    bitBucketTrigger credentialsId: 'GIT_CREDS',
      triggers: [
        [$class: 'BitBucketPPRPullRequestServerTriggerFilter',
          actionFilter: [$class: 'BitBucketPPRPullRequestServerCreatedActionFilter',
            allowedBranches: ''
          ]
        ],
        [$class: 'BitBucketPPRPullRequestServerTriggerFilter',
          actionFilter: [$class: 'BitBucketPPRPullRequestServerMergedActionFilter',
            allowedBranches: ''
          ]
        ],
        [$class: 'BitBucketPPRPullRequestServerTriggerFilter',
          actionFilter: [$class: 'BitBucketPPRPullRequestServerSourceUpdatedActionFilter',
            allowedBranches: ''
          ]
        ]
      ]
  }

  agent any

  stages {
    stage('Checkout Bitbucket repo') {
      steps {
        script {
          git branch: 'env.CHANGE_BRANCH',
            credentialsId: 'GIT_CREDS',
            url: env.GIT_URL
        }
      }
    }
    stage('Start the build') {
      steps {
        script {
            sh 'echo "BUILD"'
        }
      }
    }
  }
}

错误日志 #

stderr: fatal: ambiguous argument '0648334d4491907a45a840a7326c3b8f54180144^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

解决思路 #

1. 修正环境变量引用错误 #

原Jenkinsfile中branch: 'env.CHANGE_BRANCH'的写法错误，引号会将其视为字符串字面量，而非读取环境变量。应改为：

git branch: env.CHANGE_BRANCH, credentialsId: 'GIT_CREDS', url: env.GIT_URL

2. 手动添加Fork仓库远程并拉取代码 #

对于Fork仓库的PR，默认仅克隆源仓库无法获取Fork中的提交，需手动添加Fork远程并拉取：

stage('Checkout Bitbucket repo') {
  steps {
    script {
      // 克隆源仓库
      git credentialsId: 'GIT_CREDS', url: env.GIT_URL
      // 从PR地址提取Fork仓库Git地址并添加为远程
      def forkRepoUrl = env.CHANGE_URL.split('/pull-requests/')[0] + '.git'
      sh "git remote add fork ${forkRepoUrl}"
      // 拉取Fork仓库的目标分支
      sh "git fetch fork ${env.CHANGE_BRANCH}"
      // 切换到该分支
      sh "git checkout ${env.CHANGE_BRANCH}"
    }
  }
}

3. 使用插件内置的checkout步骤 #

Bitbucket Push and Pull Request插件提供了bitbucketCheckout步骤，可自动处理源仓库与Fork仓库的PR拉取，无需手动配置远程：

stage('Checkout Bitbucket repo') {
  steps {
    bitbucketCheckout credentialsId: 'GIT_CREDS'
  }
}

4. 验证凭证权限 #

确保GIT_CREDS凭证拥有Fork仓库的读取权限，若Fork为私有仓库，需保证凭证能正常访问该仓库。

内容的提问来源于stack exchange，提问作者airdata