Jenkins Jenkis CLI不工作:警告:无标头';X-SSH-Endpoint';詹金斯返回
我有Jenkins Jenkis CLI不工作:警告:无标头';X-SSH-Endpoint';詹金斯返回,jenkins,jenkins-cli,Jenkins,Jenkins Cli,我有Jenkins。2.205在windows10中,我有以下情况 Configure Global Security已选中Enable Security 我创建了id\u rsa\u jenkins和id\u rsa\u jenkins.pub键。公钥的值已在SSH public Keys中为我的帐户添加到Jenkins中 我有jenkins cli.jar文件,从http://localhost:9090/cli/ CLI 当我执行以下操作时(为了演示目的拆分为多行): 出现: Ente
Jenkins。2.205
在windows10
中,我有以下情况
已选中Configure Global Security
Enable Security
- 我创建了
和id\u rsa\u jenkins
键。公钥的值已在id\u rsa\u jenkins.pub
中为我的帐户添加到Jenkins中SSH public Keys
- 我有
文件,从jenkins cli.jar
http://localhost:9090/cli/
Enter passphrase for C:\Users\windowsusername\.ssh\id_rsa_jenkins:
问题
我写下有效的密码短语,然后出现以下内容:
Nov 23, 2019 11:28:22 AM org.apache.sshd.common.util.security.AbstractSecurityProviderRegistrar getOrCreateProvider
INFO: getOrCreateProvider(EdDSA) created instance of net.i2p.crypto.eddsa.EdDSASecurityProvider
Nov 23, 2019 11:28:22 AM hudson.cli.SSHCLI sshConnection
WARNING: No header 'X-SSH-Endpoint' returned by Jenkins
如上所示,未显示预期数据
任何Jenkins CLI
命令都会发生这种情况,例如:
- 帮助
- 我是谁
- 列出工作
- 已安装
插件SSH
- 在
中,在Configure Global Security
部分(底部),继续启用它,在这种情况下,我使用SSH Server
值选项Fixed
random
选项只对jenkins cli.jar
案例有用。这是因为通过SSH
连接(即:SSH-l jenkinsusername-p 2020 localhost list jobs
)必须知道端口,在本例中为2020
因此,Fixed
或Random
适用于jenkins cli.jar
(它不要求使用端口号),但对于SSH
连接,必须知道端口号(此处Fixed
需要它)
进一步说明:
Configuration
By default, Jenkins will listen on a random available port, so as not to break
existing deployments. But this is most likely not very useful, so the administrator
is encouraged to change this from the global security configuration page by assigning
a fixed port. This configuration UI will also allow you to disable this feature.
这段视频非常有价值:
- 已安装
插件SSH
- 在
中,在Configure Global Security
部分(底部),继续启用它,在这种情况下,我使用SSH Server
值选项Fixed
random
选项只对jenkins cli.jar
案例有用。这是因为通过SSH
连接(即:SSH-l jenkinsusername-p 2020 localhost list jobs
)必须知道端口,在本例中为2020
因此,Fixed
或Random
适用于jenkins cli.jar
(它不要求使用端口号),但对于SSH
连接,必须知道端口号(此处Fixed
需要它)
进一步说明:
Configuration
By default, Jenkins will listen on a random available port, so as not to break
existing deployments. But this is most likely not very useful, so the administrator
is encouraged to change this from the global security configuration page by assigning
a fixed port. This configuration UI will also allow you to disable this feature.
这段视频非常有价值: