-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins 2.32
Pipeline: Shared Groovy Libraries 2.7
GitHub Branch Source Plugin 2.0.4
-
-
workflow-cps-global-lib 2.14 https://github.com/jenkinsci/mercurial-plugin/releases/tag/mercurial-2.7
In my GitHub Org job (using GitHub Enterprise), I added a pipeline lib source that is in GitHub. If the scan credential is scoped to the job (created in the job, vs created in the global credential store), there are two problems:
1) The config page under branch shows an error instead of "Currently maps to revision: $SHA".
2) If using a job-scoped credential, the "git fetch" in the job execution does not contain a line saying "Setting GIT_ASKPASS ..."
If I switch to the identical credential stored in the global scope, both the config page and the git fetch (GIT_ASKPASS) works.
I can give more details or try to isolate the problem if needed (standalone, minimal sets of plugins).
![dots-team Config [Jenkins] 2017-08-16 12-54-50.jpg](/secure/attachment/39304/dots-team%20Config%20%5BJenkins%5D%202017-08-16%2012-54-50.jpg)
- relates to
-
-
- Closed
-
- links to
[JENKINS-43802] Shared Library using folder-scoped credential fails to authenticate
Justin Vallon
created issue -
Justin Vallon
added a comment - So, you believe this should work? I'll try to reproduce from a clean config, if that is the case.
Justin Vallon
added a comment - So, you believe this should work? I'll try to reproduce from a clean config, if that is the case. If you mean defining credentials in the organization folder’s configuration screen, then yes it ought to work.
Wilm Schomburg
added a comment - I have the same problem. It's possible to select ssh folder-scoped credentials in the job configuration for the Shared Library, but they didn't work. It only works with global credentials for me. I tested the ssh key and it's correct.
Wilm Schomburg
added a comment - I have the same problem. It's possible to select ssh folder-scoped credentials in the job configuration for the Shared Library, but they didn't work. It only works with global credentials for me. I tested the ssh key and it's correct. 
Sonny Garcia
made changes -
| Attachment | New: dots-team Config [Jenkins] 2017-08-16 12-54-50.jpg [ 39304 ] |
![dots-team Config [Jenkins] 2017-08-16 12-54-50.jpg](/secure/attachment/39304/dots-team Config [Jenkins] 2017-08-16 12-54-50.jpg){kind=link}
Sonny Garcia
added a comment - I can confirm the same behavior that wilm is seeing. I created two separate credentials for github access (same content), one inside the global Jenkins store and the other scoped to a folder. When attempting to configure access to a shared library inside the aforementioned folder, the global credential works and the folder credential does not.
I've included an attachment with the error message that shows up in the UI in the latter case. 
Here's my current environment:
- Jenkins – 2.60.2
- Pipeline: Shared Groovy Libraries – 2.8
- Credentials Plugin – 2.1.14
- GitHub Branch Source Plugin – 2.2.3
Sonny Garcia
added a comment - I can confirm the same behavior that wilm is seeing. I created two separate credentials for github access (same content), one inside the global Jenkins store and the other scoped to a folder. When attempting to configure access to a shared library inside the aforementioned folder, the global credential works and the folder credential does not.
I've included an attachment with the error message that shows up in the UI in the latter case.
Here's my current environment:
Jenkins – 2.60.2
Pipeline: Shared Groovy Libraries – 2.8
Credentials Plugin – 2.1.14
GitHub Branch Source Plugin – 2.2.3
I suspect the problem is that SCMSource.owner is not being set in this context. If so, would probably require API changes coördinated across multiple plugins to fix. TBD.
| Labels | New: cloudbees-internal-steel |
| Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Offhand sounds like a configuration error, though I am not sure. May depend on the particular retrieval method in use.