Hi there!

I belive you are not alone in the struggle of using SSH to windows slaves.
However, we do use vanilla SSHSlaves plugin for that and it works perfectly 
-- with regard to the paths part.

On Tuesday, June 17, 2014 3:44:08 AM UTC+4, Suresh Nallamilli wrote:
>
> Hi All,
>
>  
>
> I am working on a sample plugin to dynamically provision windows slaves.
>
> Windows slave images are preconfigred with SSH server(cygwin openssh 
> server), 
>
> so after provionsing - machine comes up with ssh server installed.
>
>  
>
> Once the slave is up , I am able to copy slave.jar and also able to 
> execute commands using ssh.
>
> However when I try to set the channel using below code – getting error 
> (see below stack trace)
>
> computer.setChannel(sess.getStdout(),sess.getStdin(),logger,new Listener() 
> {
>
> public void onClosed(Channel channel, IOException cause) {
>
>             sess.close();
>
>             conn.close();
>
>       }
>
>       });
>
>  
>
>  
>
> *Question:*
>
> 1)  Is windows slaves launch supported via ssh? 
>
> What steps I need to take care to add ssh launch method support for 
> windows slaves?
>
>          I am not seeing ssh support for windows slaves when adding node 
> manually , so wondering if this is supported or not?
>
>  
>
> Stack Trace:
>
>   java.io.EOFException: unexpected stream termination
>
>         at 
> hudson.remoting.ClassicCommandTransport.create(ClassicCommandTransport.java:100)
>
>         at hudson.remoting.Channel.<init>(Channel.java:392)
>
>         at hudson.remoting.Channel.<init>(Channel.java:388)
>
>         at hudson.remoting.Channel.<init>(Channel.java:349)
>
>         at hudson.remoting.Channel.<init>(Channel.java:345)
>
>  
>
>  
>
> Thanks,
>
> Suresh Nallamilli.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to