如何使用SSH代理在jenkins中配置从节点

Question

我正在使用SSH代理在Jenkins中配置一个从属节点，但出现以下错误：

[10/31/17 15:23:37] [SSH] Checking java version of java
[10/31/17 15:23:37] [SSH] java -version returned 1.8.0_151.
[10/31/17 15:23:37] [SSH] Starting sftp client.
[10/31/17 15:23:37] [SSH] Remote file system root /var/jenkins does not exist. W
ill try to create it... java.io.IOException: Could not copy slave.jar into /var/
jenkins on slave at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLaunche
r.java:1152) at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java
:145) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:816) at hu
dson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:793) at java.util.con
current.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolEx
ecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoo
lExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread
.java:748) Caused by: java.io.IOException: Failed to mkdir /var/jenkins at hudso
n.plugins.sshslaves.SFTPClient.mkdirs(SFTPClient.java:83) at hudson.plugins.sshs
laves.SSHLauncher.copySlaveJar(SSHLauncher.java:1120) ... 7 more Caused by: com.
trilead.ssh2.SFTPException: Permission denied (SSH_FX_PERMISSION_DENIED: The use
r does not have sufficient permissions to perform the operation.) at com.trilead
.ssh2.SFTPv3Client.expectStatusOKMessage(SFTPv3Client.java:555) at com.trilead.s
sh2.SFTPv3Client.mkdir(SFTPv3Client.java:955) at hudson.plugins.sshslaves.SFTPCl
ient.mkdirs(SFTPClient.java:81) ... 8 more
[10/31/17 15:23:37] Launch failed - cleaning up connection
[10/31/17 15:23:37] [SSH] Connection closed.

如何使用SSH代理在jenkins中配置从节点？

Answer 1

在Jenkins主服务器上的从属配置中，将远程根目录调整到现有目录（或允许Jenkins用户写入的目录的子目录），或在从属计算机上创建/var/jenkins并允许Jenkins用户在那里写。

Answer 2

在根据错误信息：

造成原因：com。 trilead.ssh2.SFTPException：权限被拒绝（SSH_FX_PERMISSION_DENIED：用户r没有足够的权限来执行该操作。）

确保从节点上的jenkins用户有权创建目录/ var / jenkins。

1. 登录到您的奴隶，然后运行： mkdir /var/jenkins
2. 然后将目录所有者更改为jenkins ： chown jenkins /var/jenkins
3. 从主服务器重新启动从属代理。