-
Type:
Bug
-
Resolution: Not A Defect
-
Priority:
Major
-
Component/s: ssh-slaves-plugin
-
Environment:ubunut x64 as master
win10x64 as slave
The jar file on the slave fails to start.
I use "Launch Slave Agents via SSH"
[04/06/18 15:32:05] [SSH] Opening SSH connection to 192.168.120.187:22. [04/06/18 15:32:06] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed. [04/06/18 15:32:06] [SSH] Authentication successful. [04/06/18 15:32:06] [SSH] The remote user's environment is: [04/06/18 15:32:06] [SSH] Checking java version of java [04/06/18 15:32:06] [SSH] java -version returned 1.8.0_161. [04/06/18 15:32:06] [SSH] Starting sftp client. [04/06/18 15:32:06] [SSH] Copying latest slave.jar... [04/06/18 15:32:06] [SSH] Copied 762,466 bytes. Expanded the channel window size to 4MB [04/06/18 15:32:06] [SSH] Starting slave process: cd "D:\CI\jenkins" && java -jar slave.jar <===[JENKINS REMOTING CAPACITY]===>Slave JVM has terminated. Exit code=0 [04/06/18 15:32:06] Launch failed - cleaning up connection [04/06/18 15:32:06] [SSH] Connection closed.
I use Manually trusted key Verification Strategy
Require manual verification of initinial connection is OFF
On windows, I use cygwin as bash, and openSSH from microsoft.
Java version master:
java version "1.8.0_144" Java(TM) SE Runtime Environment (build 1.8.0_144-b01) Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)
Java version slave:
java version "1.8.0_161" Java(TM) SE Runtime Environment (build 1.8.0_161-b12) Java HotSpot(TM) Client VM (build 25.161-b12, mixed mode, sharing)
The jenkins version is: Jenkins ver. 2.107.2
- is related to
-
-
- Fixed but Unreleased
-
