[JENKINS-27657] SCM workspace checkout for perforce can't access the ssh-agent

Original problem discussed in ticket JENKINS-27655">JENKINS-27655 against perforce-plugin. After discussion and investigation, I found that a similar problem for the git-plugin was fixed in ssh-agent-plugin for JENKINS-12492">JENKINS-12492, so I'm refiling this bug against ssh-agent-plugin.

Quick summary is that I have my ssh key credential loaded properly into ssh-agent-plugin, and while the key is available to the build steps themselves (such as a shell execution), the key is NOT available to the SCM/perforce step that comes before.

---
Originally reported by dayoung, imported from: SCM workspace checkout for perforce can't access the ssh-agent

• status: Open
  
• priority: Minor
  
• component(s): ssh-agent-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 20260604-211335
  

Raw content of original issue

Original problem discussed in ticket JENKINS-27655 against perforce-plugin.  After discussion and investigation, I found that a similar problem for the git-plugin was fixed in ssh-agent-plugin for JENKINS-12492, so I'm refiling this bug against ssh-agent-plugin.


Quick summary is that I have my ssh key credential loaded properly into ssh-agent-plugin, and while the key is available to the build steps themselves (such as a shell execution), the key is NOT available to the SCM/perforce step that comes before.

• environment: Ubuntu linux, chrome, Jenkins 1.606, perforce-plugin 1.3.34, ssh-agent-plugin 1.5