When the plugin throws an error when trying to execute the ssh-agent in a pipeline, it can be the case that there is no reason in the error log.
hudson.AbortException: Failed to run ssh-agent:
at PluginClassLoader for ssh-agent//com.cloudbees.jenkins.plugins.sshagent.exec.ExecRemoteAgent.(ExecRemoteAgent.java:55)
Without any reason, it is nearly impossible to debug this. Which brings me to a second point: How am I supposed to debug this now, with no useful error output?
Originally reported by 
ger_senshi, imported from: Empty variable "reason" makes error message useless
- status: Open
- priority: Minor
- component(s): ssh-agent-plugin
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 20260604-211335
Raw content of original issue
When the plugin throws an error when trying to execute the ssh-agent in a pipeline, it can be the case that there is no reason in the error log.
hudson.AbortException: Failed to run ssh-agent:
at PluginClassLoader for ssh-agent//com.cloudbees.jenkins.plugins.sshagent.exec.ExecRemoteAgent.<init>(ExecRemoteAgent.java:55)
Without any reason, it is nearly impossible to debug this. Which brings me to a second point: How am I supposed to debug this now, with no useful error output?
environment
Jenkins Controller: Win Server 2022, Jenkins 2.462.1<br/>
Jenkins Agent: Win Server 2022<br/>
Plugin version: 376.v8933585c69d3
When the plugin throws an error when trying to execute the ssh-agent in a pipeline, it can be the case that there is no reason in the error log.
Without any reason, it is nearly impossible to debug this. Which brings me to a second point: How am I supposed to debug this now, with no useful error output?
Originally reported by
ger_senshi, imported from: Empty variable "reason" makes error message useless
Raw content of original issue
environment