-
Bug
-
Resolution: Incomplete
-
Minor
I had an SSH credential added before starting to use the sshagent workflow step and I was unable to refer to the credential by name (JENKINS-32101) or even by ID. Not in the screenshot that it doesn't show up in the snippet generator UI either.
When referring to a credential which was previously added (2d954d6d-9eda-444a-90ff-693df2ef3f26) with:
node { sshagent(['2d954d6d-9eda-444a-90ff-693df2ef3f26']) { // do work here } }
The workflow fails to find the credential:
Running on master in /home/tyler/.jenkins/jobs/multipass/branches/master/workspace
[Workflow] node {
[Workflow] SSH Agent : Start
FATAL: [ssh-agent] Could not find specified credentials
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent] Java/JNR ssh-agent
[ssh-agent] Started.
[Workflow] sshagent {
Workaround
If I add the credential directly through the snippet generator, then I am able to refer to it from workflow.
- is related to
-
JENKINS-32101 Credentials must be referred to by ID which is Jenkins master specific
-
- Resolved
-
[JENKINS-32102] Only credentials added via the snippet generator are usable
Link |
New:
This issue is related to |
Workflow | Original: JNJira [ 167585 ] | New: JNJira + In-Review [ 182795 ] |
Labels | Original: workflow | New: pipeline workflow |
Labels | Original: pipeline workflow | New: pipeline |
Comment |
[ [~jglick] hi Jesse, I am having a similar problem to this issue except that even credentials created in the snippet generator aren't available when the Pipeline is running - they are not selectable from the dropdown. I've added more comments, logs, and screenshots here: https://issues.jenkins-ci.org/browse/JENKINS-32101 ] |
Resolution | New: Incomplete [ 4 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |