【问题标题】:sonar maven goal with sonarqube jenkins plugin - ERROR SCM provider was set to "git" but no SCM provider found for this key带有 sonarqube jenkins 插件的声纳 maven 目标 - 错误 SCM 提供程序设置为“git”,但没有找到此密钥的 SCM 提供程序
【发布时间】:2015-11-03 19:42:36
【问题描述】:

我已按照以下说明操作:http://docs.sonarqube.org/display/PLUG/Triggering+SonarQube+on+Jenkins+Job#TriggeringSonarQubeonJenkinsJob-TriggeringaProjectAnalysiswithMaven

SonarQube:5.1.1,
Jenkins SonarQube 插件:2.2.1

我对基础项目的 Maven 目标是
干净的编译器:编译

当我构建我的项目时,我从声纳后期构建任务中收到此错误:

[ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.6:sonar (default-cli) on project onu-main: SCM provider was set to "git" but no SCM provider found for this key. No SCM provider installed -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.6:sonar (default-cli) on project onu-main: SCM provider was set to "git" but no SCM provider found for this key. No SCM provider installed
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: SCM provider was set to "git" but no SCM provider found for this key. No SCM provider installed
    at org.codehaus.mojo.sonar.bootstrap.ExceptionHandling.handle(ExceptionHandling.java:41)
    at org.codehaus.mojo.sonar.bootstrap.RunnerBootstraper.execute(RunnerBootstraper.java:139)
    at org.codehaus.mojo.sonar.SonarMojo.execute(SonarMojo.java:132)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)

【问题讨论】:

  • 请您发布您的 pom.xml
  • 你安装了jenkins git插件和git客户端插件吗?
  • @tdrury 是的,我已经安装了 git 插件。我的构建工作正常。只是声纳后期构建任务失败。
  • @IkerAguayo 这是一个多模块项目,大约有 20 个 pom。我发现如果我在 SonarQube 设置中禁用 SCM 传感器,此错误就会消失,但是 SonarAnalysis 在指向我的父 pom 时不包含任何文件。如果我只使用 -pl 选项构建一个项目,那么我会收到此错误。 [错误] 无法在项目 onu-config 上执行目标 org.codehaus.mojo:sonar-maven-plugin:2.6:sonar (default-cli):无法确定项目的结构。可能您使用 Maven Advanced Reactor Options 和损坏的模块树。 "onu-test-common" 是孤儿 -> [帮助 1
  • 这个错误听起来像我在this post 上遇到的错误。是否安装了 sonar-scm-git-plugin?

标签: maven jenkins sonarqube sonarqube5.1


【解决方案1】:

使用 maven 参数调用声纳:-Dsonar.scm.disabled=true

【讨论】:

    【解决方案2】:

    您可以在 SonarQube-Server 上安装 Git 插件或从 POM 中删除 developerConnection-tag,两者都可以解决问题(已使用 SQ 5.1.1 测试)

    【讨论】:

      猜你喜欢
      • 2014-05-02
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2016-10-06
      • 2015-04-02
      • 2018-03-05
      相关资源
      最近更新 更多