|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-16274) SFTP/SCP support [email protected] (JIRA)
- [JIRA] (JENKINS-16274) SFTP/SCP support [email protected] (JIRA)
- [JIRA] (JENKINS-16274) SFTP/SCP support [email protected] (JIRA)
- [JIRA] (JENKINS-16274) SFTP/SCP support [email protected] (JIRA)
- [JIRA] (JENKINS-16274) SFTP/SCP support [email protected] (JIRA)

Yet another approach is to use "ProxyCommand=ssh -p %p jenkins.acme.com diagnose-tunnel JOBNAME" or something. This first creates an SSH connection to jenkins.acme.com and runs the diagnose-tunnel command with arguments. This can set up the relevant context, then pass on the stream to another SSH server session.
The only downside is that it does double encryption. But the ProxyCommand option can be in ~/.ssh/config, and with the wildcard support in it, the end user experience can be something like: