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

Latest version fails to find reports directory

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • clang-scanbuild-plugin
    • None
    • clang-scanbuild-plugin-1.7

      After updating to the latest version of this plugin, there has been an issue with finding the clang scan build reports directory. The plugin is configured with:

      • Mark build as unstable when threshold is exceeded? == unset/false
      • Report folder == clangScanBuildReports (default value)

      After a project, configured with the plugin has been build, the following exception is seen in the console

      ERROR: Build step failed with exception
      java.lang.NullPointerException
      	at hudson.FilePath.isAbsolute(FilePath.java:271)
      	at hudson.FilePath.resolvePathIfRelative(FilePath.java:256)
      	at hudson.FilePath.<init>(FilePath.java:252)
      	at jenkins.plugins.clangscanbuild.publisher.ClangScanBuildPublisher.perform(ClangScanBuildPublisher.java:119)
      	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723)
      	at hudson.model.Build$BuildExecution.post2(Build.java:185)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668)
      	at hudson.model.Run.execute(Run.java:1763)
      	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      	at hudson.model.ResourceController.execute(ResourceController.java:98)
      	at hudson.model.Executor.run(Executor.java:410)
      

      After some investigation into the source code, the configuration was changed to set Mark build as unstable when threshold is exceeded?== set/true (with all other values left as default), this configuration produced a successful result. The difference in behaviour with the configuration change indicates the issue is with the publisher config.jelly and its constructor, however I am not well versed enough in this area to explain why or suggest a fix.

            jkennedy1980 Josh Kennedy
            rgeddis22 Ross Geddis
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: