-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins LTS w/ github-branch-source 2.2.2
There appears to be an issue with the github-branch-source plugin where if you put a specification on a credential's domain, the credential will never be selected to authenticate when creating a GitHub Status. This appears to be because the apiUrl is not being passed when looking up the credential.
The project build log will display:
Could not update commit status. Message: {"message":"Must authenticate to access this API.","documentation_url":"https://developer.github.com/enterprise/2.9/v3"}
I've got a patch incoming and have tested it out for a hostname specification and was able to successfully have it fail before and succeed after the patch. I also reverted to 2.2.2 and the failure returned.
- mentioned in
-
Page Failed to load
[JENKINS-46364] GitHub Branch Source Plugin can't create status if credential restricted by spec
Issue Type | Original: Task [ 3 ] | New: Bug [ 1 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Remote Link | New: This issue links to "Page (Jenkins Wiki)" [ 17916 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
I have created a pull request to resolve this issue.