-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin fails to connect to container spawning jenkins slave #4
Comments
Downgraden SSH slaves to version 1.6 (instead of 1.6.1) fixed it |
I had the same problem. |
Any chance of fixing this any time soon? |
ai have tg same problem with random ssh credentials being created.. |
Same problem here, downgrading helped. Hope this issue will be fixed soon. When reading the docs I see that there should also be a "SSH Username with password" credential but I don't see it anywhere, see https://wiki.jenkins-ci.org/display/JENKINS/SSH+Slaves+plugin |
@ckulla , you downgraded what to which version exactly? |
I've bumped the ssh link to the latest version, which ought to help |
When trying to connected to the freshly spawned slave (which is perfectly ssh-able) I get the following error message in details of new node
I also noticed the plugin adds a credentials with a random (uuid) username with a copy of the original settings ssh key and as comment 127.0.0.1. Is this normal?
The text was updated successfully, but these errors were encountered: