Jenkins Pipepline失败了:从XXX远程调用JNLP 4-connect连接失败

ruoxqz4g  于 12个月前  发布在  Jenkins
关注(0)|答案(3)|浏览(475)

我的Jenkins管道在从svn checkout 时失败了。下面是错误。

Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from nobuild01.sdi.pvt/152.144.34.14:50396
        at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
        at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
        at hudson.remoting.Channel.call(Channel.java:955)
        at hudson.FilePath.act(FilePath.java:1036)
        at hudson.FilePath.act(FilePath.java:1025)
        at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:928)
        at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:864)
        at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113)
        at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85)
        at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75)
        at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
        at hudson.security.ACL.impersonate(ACL.java:290)
        at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins
    at hudson.scm.SubversionSCM.descriptor(SubversionSCM.java:2584)
    at hudson.scm.SubversionSCM.createDefaultSVNOptions(SubversionSCM.java:1085)
    at hudson.scm.SubversionSCM.createClientManager(SubversionSCM.java:1075)
    at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1002)
    at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:979)
    at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2918)
    at hudson.remoting.UserRequest.perform(UserRequest.java:212)
    at hudson.remoting.UserRequest.perform(UserRequest.java:54)
    at hudson.remoting.Request$2.run(Request.java:369)
    at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
    at java.lang.Thread.run(Thread.java:745)
Caused: java.io.IOException: Remote call on JNLP4-connect connection from nobuild01.sdi.pvt/152.144.219.14:50396 failed
    at hudson.remoting.Channel.call(Channel.java:961)
    at hudson.FilePath.act(FilePath.java:1036)
Caused: java.io.IOException: remote file operation failed: c:\Dev at hudson.remoting.Channel@4b1b30ed:JNLP4-connect connection from nobuild01.sdi.pvt/152.144.34.14:50396
    at hudson.FilePath.act(FilePath.java:1043)
    at hudson.FilePath.act(FilePath.java:1025)
    at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:928)
    at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:864)
    at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113)
    at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85)
    at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75)
    at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
    at hudson.security.ACL.impersonate(ACL.java:290)
    at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)

从机运行在openJDK上,而不是Oracle Java上。所以我用IcedTea来运行. jnlp。我检查了我的Jenkins服务是否正在运行。
打开日期:java-1.8.0-openjdk-1.8.0.91-3
也有人公会我在哪里我可以看到Jenkins日志。Jenkins Master是一个Docker容器。

23c0lvtd

23c0lvtd1#

1.对于Windows,转到服务(开始→运行:services.xml),找到Jenkins和Jenkins Agent,右键单击→重新启动。
1.如果没有帮助(UI没有响应),打开Windows任务管理器→进程,杀死java.exe进程,然后再次重新启动服务。

ps -ef | grep jenkins
sudo kill -9 <pid>
pepwfjgg

pepwfjgg2#

这可能是由于jenkins上的refSpec配置。在源代码管理中,提供SSH,github/任何其他git REPO URL。点击高级按钮并在RefSpec中提供**“refs/pull/:refs/remotes/origin/pr/"**
在上面的配置中,粗体内容可能会产生问题,请删除并重新启动您的jenkins。
在我的情况下,这为我解决了问题。

bfrts1fy

bfrts1fy3#

我们在“git clone”期间得到了标题中的错误,但没有后面的“NoClassDefFoundError”。我们通过缩短作业名称解决了这个问题。
它本身并不太长,但是当前面加上作业的文件夹名称时,存储库中文件的路径变得太长了。显然这影响了克隆人的行动。

相关问题