search

jenkinsci / publish-over-ssh-plugin

https://plugins.jenkins.io/publish-over-ssh/
115 stars 150 forks source link

[JENKINS-54129] Jump Hosts need their own configuration #99

Open jira-importer opened 5 years ago

jira-importer commented 5 years ago

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.

Originally reported by mlehmann, imported from: Jump Hosts need their own configuration
  • status: Open
  • priority: Major
  • resolution: Unresolved
  • imported: 2022/01/10
theruffus commented 5 months ago

I don't think JumpHost even works as it is... I get: jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection. Message: [Failed to connect session for config [Debian 5]. Message [java.net.ConnectException: Connection timed out: getsockopt]]

when trying to connect using it... Works fine on my ssh client.