-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 2.504.1
Github Branch Source Pugin 1815.v9152b_2ff7a_1b_
Description:
When using the Jenkins GitHub App integration with a multibranch pipeline, Jenkins successfully detects branches created by GitHub Copilot, but fails (example log: Could not find user Copilot for pull request 188.) to detect pull requests created by the same GitHub App user.
As a result, these pull requests do not appear in the multibranch pipeline view, and their corresponding jobs are not created.
This issue affects visibility and CI validation of PRs authored by GitHub Apps like Copilot witch in turn is linked to our ability to merge those PRs in Github Web.
Steps to Reproduce:
- Configure a Jenkins GitHub Organization or multibranch pipeline using the GitHub App credential.
- Trigger a scan of the repository.
- Observe:
- Branches created by GitHub Copilot (e.g., copilot/branch-name) appear in Jenkins.
- Pull requests authored by GitHub Copilot do not show up in the job list.
- Jenkins logs contain an "warning" like:
Checking branch copilot/fix-187 'jenkins/ci/Jenkinsfile' found Met criteria Changes detected: copilot/fix-187 (null → 1061b95307b6db908c31c1a8e20a520fcd704327) Did not schedule build for branch: copilot/fix-187 8 branches were processed Checking pull-requests... Getting remote pull requests... Could not find user Copilot for pull request 188.
Additional info:
The same flow works fine with dependabot created automatic PRs/branches.