-
Improvement
-
Resolution: Incomplete
-
Major
-
None
-
Jenkins ver. 2.138.2
Publish Over SSH ver. 1.20.1
Windows 10 / Windows Server 2016
Jump Hosts need their own configuration including port and credentials.
You have added support for jump hosts but I don't see any kind of configuration for them. By checking the source on github it seems they are using the same settings as the server (credentials + ports) and that makes them useless in our environment because our jump server are not using the same ports and credentials as the exposed systems (that would be crazy security design 
).
A way to utilize most of the current infrastructure could be a way to define the jump hosts as server entry in the global configuration and link the current field against the defined server.
[JENKINS-54129] Jump Hosts need their own configuration
Closing ticket, please use the corresponding Github Issue as linked above.
For your information, all publish-over-ssh component type JENKINS issues related to the Publish Over SSH plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues
Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues/99
And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-ssh-plugin/issues?q=%22JENKINS-54129%22
(Note: this is an automated bulk comment)