-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins:
Jenkins core 2.64 on Ubuntu 15.04
Experimental update center enabled
Branch UX versions of plugins as follows:
cloudbees-bitbucket-branch-source 2.2.0-alpha-4
branch-api 2.0.11-alpha-1
blueocean-pipeline-editor 1.0-alpha-4
mercurial 2.0-alpha-4
github-branch-source 2.2.0-alpha-4
scm-api 2.2.0-alpha-1
git 3.4.0-alpha-4
Jenkins: Jenkins core 2.64 on Ubuntu 15.04 Experimental update center enabled Branch UX versions of plugins as follows: cloudbees-bitbucket-branch-source 2.2.0-alpha-4 branch-api 2.0.11-alpha-1 blueocean-pipeline-editor 1.0-alpha-4 mercurial 2.0-alpha-4 github-branch-source 2.2.0-alpha-4 scm-api 2.2.0-alpha-1 git 3.4.0-alpha-4
Summary:
Given a GitHub API token known to work elsewhere, I am unable to access private repositories while configuring a multibranch pipeline project using GitHub as a source.
Steps to recreate:
1. Create a new Multibranch Pipeline project
2. Select GitHub as your API endpoint.
3. Supply a credential, and an owner, which has been used successfully elsewhere to access private repos. Shown below is this owner and credential being used with the Alpha plugins. In this case the `quality-assurance` repo is not available. I believe this is because it is a private repo.
4. As a control, try with another Jenkins instance, one which is not running the alpha code. Same GitHub ID for the owner, same GitHub API token in use. The list now shows all of the repos, both public and private, including `quality-assurance`:
- links to
