Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-19014

Sonar installation not available to standalone runner build steup

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • sonar-plugin
    • None
    • Jenkins 1.525, Sonar Plugin 2.1, linux

      Upon upgrading from 1.523 to 1.525 (skipped 1.524) The Invoke Standalone Sonar Analysis field shows "Needs to know where your Sonar is installed. Please do so from the system configuration." In the Sonar Installation field.

      The system configuration screen has a sonar runner installation configured.

      Jenkins Sonar jobs fail with:
      FATAL: null
      java.lang.NullPointerException
      at hudson.plugins.sonar.SonarInstallation.all(SonarInstallation.java:38)
      at hudson.plugins.sonar.SonarInstallation.get(SonarInstallation.java:46)
      at hudson.plugins.sonar.SonarRunnerBuilder.isSonarInstallationValid(SonarRunnerBuilder.java:285)
      at hudson.plugins.sonar.SonarRunnerBuilder.perform(SonarRunnerBuilder.java:187)
      at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
      at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
      at hudson.model.Build$BuildExecution.build(Build.java:199)
      at hudson.model.Build$BuildExecution.doRun(Build.java:160)
      at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586)
      at hudson.model.Run.execute(Run.java:1593)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:247)

      This all worked on 1.523. I have tried removing and re-adding the Sonar installation from the system configuration and from the job. Neither have solved the problem.

          [JENKINS-19014] Sonar installation not available to standalone runner build steup

          Max Spring added a comment -

          I don't see how the Jenkow plugin is involved in this problem.
          Can you please shed some more light on this aspect?

          Max Spring added a comment - I don't see how the Jenkow plugin is involved in this problem. Can you please shed some more light on this aspect?

          Gavin Swanson added a comment -

          Sorry about that I when I was filling it out I read that as Jenkins-Plugin.

          Gavin Swanson added a comment - Sorry about that I when I was filling it out I read that as Jenkins-Plugin.

          Gavin Swanson added a comment -

          Is this possibly related to JENKINS-18994 they were filed around the same time and both produce NPEs.

          Gavin Swanson added a comment - Is this possibly related to JENKINS-18994 they were filed around the same time and both produce NPEs.

          Tim Mace added a comment -

          I have seen exactly the same problem. 1.523 is fine but the issue appears in 1.524 and is still present in 1.529

          Tim Mace added a comment - I have seen exactly the same problem. 1.523 is fine but the issue appears in 1.524 and is still present in 1.529

          Tobias G added a comment -

          This is still present in 1.530 as well.
          It seems like we only can configure sonar-runners, but no sonar instances at all.
          The option to define sonar server, db-connections username and so on seems to be gone.

          http://docs.codehaus.org/download/attachments/227052831/sonar-installation.png

          This step is not present at all. Maybe this should be reported to the sonar-plugin instead?

          Tobias G added a comment - This is still present in 1.530 as well. It seems like we only can configure sonar-runners, but no sonar instances at all. The option to define sonar server, db-connections username and so on seems to be gone. http://docs.codehaus.org/download/attachments/227052831/sonar-installation.png This step is not present at all. Maybe this should be reported to the sonar-plugin instead?

          Similar issue with 1.554. Disabling the Maven integration plugin triggers the NullPointerException and the message described above.

          Dimitris Stafylarakis added a comment - Similar issue with 1.554. Disabling the Maven integration plugin triggers the NullPointerException and the message described above.

            m2spring Max Spring
            s7726 Gavin Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: