We have 2 instances of Jenkins setup - 1 for QA purposes like testing Jenkins upgrades, new plugin installs etc.
We use Github branch source plugin to contact Github Enterprise. Recently, we noticed that the Discover pull requests from forks with Trust: From users with Admin or Write access (or Nobody for that matter) isn't working as intended in one of the instances.
The QA instance pipeline seems to run without any issues whereas in the PROD instance, PR build triggered by forks from users with only Read access fails with the following:
Connecting to https:Connecting to https:Loading trusted files from base branch master at target_commit_hash rather than source_commit_hash
GitHub has been notified of this commit’s build result
hudson.plugins.git.GitException: Command "git fetch --tags --progress --prune origin +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout:
stderr: remote: Repository not found.
fatal: repository 'https: not foundat org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2450)
I'm not quite sure how to debug this since the behavior is pretty strange. This is blocking some of our teams since they want readers to be able to create/run builds for forked PRs.