简体   繁体   English

添加构建后动作Sonar会导致Jenkins构建失败

[英]Adding Post-build Actions Sonar causes Jenkins build to fail

Using Jenkins ver. 使用Jenkins版本。 1.494; 1.494; Jenkins Sonar Plugin 2.0.1 ; 詹金斯声纳插件2.0.1 ; Sonar server 3.4.1. 声纳服务器3.4.1。 Maven job. Maven的工作。

Adding Post-build Actions Sonar causes Jenkins build to fail (ERROR: Failed to parse POMs). 添加构建后操作Sonar会导致Jenkins构建失败(错误:无法解析POM)。 Deleting Sonar action then again makes it pass. 然后再次删除声纳动作即可使其通过。

Sync complete, took 35 ms
Parsing POMs
[Atlas_Phevos] $ java -Xmx512m -XX:MaxPermSize=128m -cp /home/jenkins/jenkins-home/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/home/jenkins/jenkins-home/tools/Maven/Maven304/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /home/jenkins/jenkins-home/tools/Maven/Maven304 /usr/local/tomcat-6.0.32/webapps/jenkins/WEB-INF/lib/remoting-2.19.jar /home/jenkins/jenkins-home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 60147
ERROR: Failed to parse POMs
java.io.IOException: Cannot run program "java" (in directory "/home/jenkins/jenkins-home/workspace/Atlas_Phevos"): java.io.IOException: error=2, No such file or directory
    at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
    at hudson.Proc$LocalProc.<init>(Proc.java:244)
    at hudson.Proc$LocalProc.<init>(Proc.java:216)
    at hudson.Launcher$LocalLauncher.launch(Launcher.java:763)
    at hudson.Launcher$ProcStarter.start(Launcher.java:353)
    at hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:223)
    at hudson.maven.ProcessCache.get(ProcessCache.java:231)
    at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:670)
    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586)
    at hudson.model.Run.execute(Run.java:1543)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
    at hudson.model.ResourceController.execute(ResourceController.java:88)
    at hudson.model.Executor.run(Executor.java:236)
Caused by: java.io.IOException: java.io.IOException: error=2, No such file or directory
    at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
    at java.lang.ProcessImpl.start(ProcessImpl.java:65)
    at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)
    ... 12 more
Skipping sonar analysis due to bad build status FAILURE
Sending e-mails to: ____
Finished: FAILURE

I haven't put updated setting.xml on Jenkins server, I guess Jenkins should take its own configuration for Sonar (sever, JDBC connection etc.) 我没有在Jenkins服务器上放置更新的setting.xml ,我想Jenkins应该为Sonar采用自己的配置(服务器,JDBC连接等)。

UPDATE: Problem still exists. 更新:问题仍然存在。 I tried several jobs to start sonar analysis. 我尝试了几项工作来开始声纳分析。

From your exception it looks like Jenkins cannot find your JDK. 从您的异常看来,Jenkins找不到您的JDK。 In your job configuration you can expand the Sonar properties. 在您的作业配置中,您可以扩展Sonar属性。 Make sure that a valid JDK from your Jenkins config is selected under the JDK option. 确保在JDK选项下选择了来自Jenkins配置的有效JDK。

While you are looking at the properties make sure the pom file specified under Root POM is correct. 在查看属性时,请确保“ Root POM下指定的pom文件正确。

Try that... 试试看...

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM