|
||||||||
|
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)
Another possibility is to send environment variable via -oSendEnv=CONTEXT. A wrapper script needs to be provided to actually invoke it with "export CONTEXT=diagnose JOBNAME".
Yet another hack is to use remote-to-local port forwarding as the information carrying mechanism in the host name portion ("-oRemoteForward=9999 ThisCanBeArbitraryText:1234", except ThisCanBeArbitraryText can't really be an arbitrary text because it needs to look like a host name.