收集静态分析结果时,我在Jenkins从属节点上的作业失败。
相同的作业在Jenkins主节点上运行良好。我尝试使用ssh凭据或通过“执行命令”连接Jenkins,结果相同。
主服务器和从服务器使用相同的Java版本:OpenJDK Zulu 8.20.0.5-linux64。
我试图清理Maven repo、. jenkins/缓存和slave.jar-没有帮助。slave.jar是正确的文件,md5与主文件匹配。
静态分析收集器插件是最新版本(1.50)。Checkstyle插件也是最新版本(3.47)。詹金斯的版本是1.642.3。
00:02:49.892 [INFO] ------------------------------------------------------------------------
00:02:49.892 [INFO] BUILD SUCCESS
00:02:49.892 [INFO] ------------------------------------------------------------------------
00:02:49.892 [INFO] Total time: 01:58 min
00:02:49.892 [INFO] Finished at: 2017-02-07T23:13:52+02:00
00:02:50.165 [INFO] Final Memory: 48M/1332M
00:02:50.165 [INFO] ------------------------------------------------------------------------
00:02:50.197 ###################################################################
00:02:50.197 job-exporter plugin started
00:02:50.197 hudson.version: 1.642.3
00:02:50.197 host:
00:02:50.197 id: 11
00:02:50.197 duration: 2 min 50 sec
00:02:50.197 slave: jenkins-slave
00:02:50.197 started: 2017-02-07T23:11:02
00:02:50.197 result: SUCCESS
00:02:50.197 summary: Executor #3 for jenkins-slave : executing phb-test-1 #11
00:02:50.197 executor: 3
00:02:50.197 elapsedTime: 170200
00:02:50.197 number: 11
00:02:50.198 jobName: phb-test-1
00:02:50.198 gitBranch: origin/master
00:02:50.198 we have 1 build cause:
00:02:50.241 Cause.UserIdCause Started by user ---
00:02:50.241 user.id: ---
00:02:50.241 user.name: --- --- (---)
00:02:50.241 user.fullName: --- --- (---)
00:02:50.241 user.emailAddress: ---@---.com
00:02:50.247 new file written: /root/workspace/phb-test-1/hudsonBuild.properties
00:02:50.247 job-exporter plugin finished. That's All Folks!
00:02:50.247 ###################################################################
00:02:50.430 [CHECKSTYLE] Collecting checkstyle analysis files...
00:02:51.087 ERROR: Build step failed with exception
00:02:51.087 java.lang.NullPointerException
00:02:51.089 at org.apache.commons.digester3.Digester.getXMLReader(Digester.java:799)
00:02:51.089 at org.apache.commons.digester3.Digester.parse(Digester.java:1642)
00:02:51.089 at org.apache.commons.digester3.Digester.parse(Digester.java:1745)
00:02:51.089 at hudson.plugins.checkstyle.parser.CheckStyleParser.parse(CheckStyleParser.java:67)
00:02:51.089 at hudson.plugins.analysis.core.AbstractAnnotationParser.parse(AbstractAnnotationParser.java:54)
00:02:51.089 at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:325)
00:02:51.089 at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:283)
00:02:51.089 at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:234)
00:02:51.089 at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:203)
00:02:51.089 at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31)
00:02:51.089 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2719)
00:02:51.089 at hudson.remoting.UserRequest.perform(UserRequest.java:120)
00:02:51.089 at hudson.remoting.UserRequest.perform(UserRequest.java:48)
00:02:51.089 at hudson.remoting.Request$2.run(Request.java:326)
00:02:51.089 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
00:02:51.089 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
00:02:51.089 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
00:02:51.089 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
00:02:51.089 at java.lang.Thread.run(Thread.java:745)
00:02:51.089 at ......remote call to ph-jenkins-slave-ntn(Native Method)
00:02:51.089 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
00:02:51.089 at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
00:02:51.089 at hudson.remoting.Channel.call(Channel.java:781)
00:02:51.089 at hudson.FilePath.act(FilePath.java:979)
00:02:51.089 at hudson.FilePath.act(FilePath.java:968)
00:02:51.089 at hudson.plugins.checkstyle.CheckStylePublisher.perform(CheckStylePublisher.java:78)
00:02:51.089 at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:68)
00:02:51.089 at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:295)
00:02:51.089 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)
00:02:51.089 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
00:02:51.089 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782)
00:02:51.089 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723)
00:02:51.089 at hudson.model.Build$BuildExecution.post2(Build.java:185)
00:02:51.089 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668)
00:02:51.089 at hudson.model.Run.execute(Run.java:1763)
00:02:51.089 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
00:02:51.089 at hudson.model.ResourceController.execute(ResourceController.java:98)
00:02:51.089 at hudson.model.Executor.run(Executor.java:410)
00:02:51.089 Build step 'Publish Checkstyle analysis results' marked build as failure
00:02:51.096 Finished: FAILURE
当我为组织启用日志时。阿帕奇。平民消化器3。消化器类别,我还看到以下例外情况:
Feb 07, 2017 11:13:53 PM SEVERE org.apache.commons.digester3.Digester getParser
Digester.getParser:
java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
at javax.xml.parsers.SAXParserFactory.setSchema(SAXParserFactory.java:394)
at org.apache.commons.digester3.Digester.getFactory(Digester.java:441)
at org.apache.commons.digester3.Digester.getParser(Digester.java:652)
at org.apache.commons.digester3.Digester.getXMLReader(Digester.java:799)
at org.apache.commons.digester3.Digester.parse(Digester.java:1642)
at org.apache.commons.digester3.Digester.parse(Digester.java:1745)
at hudson.plugins.checkstyle.parser.CheckStyleParser.parse(CheckStyleParser.java:67)
at hudson.plugins.analysis.core.AbstractAnnotationParser.parse(AbstractAnnotationParser.java:54)
at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:325)
at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:283)
at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:234)
at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:203)
at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2719)
at hudson.remoting.UserRequest.perform(UserRequest.java:120)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
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 java.lang.Thread.run(Thread.java:745)
非常感谢。
我注意到主节点上有-Djavax。xml。解析器。SAXParserFactory=com。太阳组织。阿帕奇。薛西斯。内部的jaxp。正在运行的进程的SAXParserFactoryImpl
参数。我在从属节点定义中添加了与VM参数相同的参数,现在可以正常工作了。
我想和Kubernetes一起经营jenkins。我能够成功地使用jenkins kubernetes插件连接到kubernetes。现在,我正在运行一个管道示例,但是在运行过程中,我总是得到一个错误,上面写着: 它就挂在那里。如果我使用检查pods,我会看到pod正在运行,然后状态更改为completed,然后它就消失了。然后另一个名字相似的豆荚,开始和结束,循环继续。这些豆荚的最后一种状态如下
我想知道以下情况是否可能,请帮助我:- 情景1:- 我把我的本地系统作为Jenkins主系统,每次我需要一个从系统来运行自动化测试脚本时,docker容器就会作为Jenkins从系统旋转起来,我的脚本就会在从系统上执行,执行完成后容器就会被销毁。 我可以旋转多个容器作为Jenkins从本地系统作为Jenkins主。 谢谢
问题 我已经将Csanchez的jenkins-kubernetes插件(版本0.12)部署到本地的Minikube/Kubernetes环境中。在Jenkins UI中配置pod模板和容器模板时,pod会自动生成并处理简单的作业。然而,当POD模板和容器模板在管道脚本中定义时,Jenkins Master拒绝连接,称POD已经连接到Master。 环境 minikube版本:V0.20.0 Ku
我正在尝试将我的windows slave作为服务连接到jenkins 2.88。我通过webstart启动了这个奴隶,然后运行jenkins奴隶。exe install来安装服务。第二次运行作业时,从svn中检出内容,我得到以下错误: 该服务正在以“我的用户”身份运行,以使其具有所有必要的权限。简而言之,我的问题是jenkins是否正确支持从服务运行jenkins slave jar的方法。例如
背景信息:我有一个Kubernetes集群,有3个linux节点和1个windows节点。从詹金斯大师到特工的一切都在一个由库伯奈斯控制的容器或吊舱里。 我试图将Windows代理(在容器中)连接到Linux主服务器(也在容器中),但在使用hudson.remoting.jnlp将从服务器连接到主服务器时遇到了问题。 以下是该命令的错误: 我尝试匹配master和slave的Java版本,使用最新
然而,在我创建了另一个docker服务器并创建了其中两个服务器的群并再次尝试运行jenkins jobs之后,它仍然只在原始服务器(现在也是一个管理器)上部署容器。我希望swarm能够平衡负载,并在swarm中均匀地分配新创建的容器。我错过了什么? 也许我必须使用服务吗?