|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Still true in dev sources from today (5b91c6b)—unless I check the newly available checkbox Bind all declared ports, in which case it suddenly works. (With username/password authentication, not SSH private key, contradicting the original claim in this issue.) Why would this not be the default? Or why would port 22 at least not be bound, since DockerComputerLauncher expects it to be? And how are you supposed to attach a slave using the latest released version, 0.7, which lacks this option?
(The lack of any help-*.html files covering the meaning and syntax of various fields makes it hard to even tell what you are supposed to do in the normal case.)
Also BTW every time it fails in this way, it leaves behind a container that it fails to clean up.