[JIRA] (JENKINS-59016) GitHub branch source won't scan with folder scoped credentials

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title

Mark Waite updated an issue   Jenkins / JENKINS-59016 GitHub branch source won't scan with folder scoped credentials Change By: Mark Waite If I define a credential at the root level, then the GitHub branch source can use the credential to scan the repository for branches.  If I define the credential in a folder, then the GitHub branch source accepts the credential, but then the scan log reports: {code} Started [Tue Aug 20 13:00:40 MDT 2019] Starting branch indexing... 13:00:40 Connecting to https://api.github.com with * no credentials * , anonymous access {code} Without the credentials, scanning of private repositories is not allowed and scanning of public repositories is limited by a much smaller value for the GitHub API rate limit. ||Version||Result|| ||2.5.6||Credentials ignored| ||2.5.5||Credentials ignored| ||2.5.4|Credentials honored| ||2.5.3|Credentials honored| ||2.4.5|Credentials honored| ||2.3.6|Credentials honored| Refer to the [JENKINS-59016 branch in my jenkins-bugs repo|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-59016] for the Jenkins Pipeline that I use to test this.  The jobs are run from inside a Docker image that I use which includes credentials used to access the repository. Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201369.1566328715000.7175.1566407880203%40Atlassian.JIRA.