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

reports 0 bugs if workspace path contains spaces

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • clang-scanbuild-plugin
    • None
    • Hudson 1.447, clang plugin 1.2

      My job name contains spaces. It looks like these are not correctly handled by the clang plugin. In the command line below, forward slashes appear before the spaces, where it should have backslashes.

      EXECUTING COMMAND:[/opt/checker/scan-build, -k, -v, -v, -o, /mnt/build/hudson/jobs/My/ Job/builds/2011-04-05_10-15-41/clangScanBuildReports, xcodebuild, -target, MyApp, -configuration, Debug, -sdk, iphonesimulator, clean, build]
[My Job] $ /opt/checker/scan-build -k -v -v -o "/mnt/build/hudson/jobs/My/ Job/builds/2011-04-05_10-15-41/clangScanBuildReports" xcodebuild -target MyApp -configuration Debug -sdk iphonesimulator clean build
scan-build: Emitting reports for this run to '/var/folders/+M/+MPgEtXNHEmEUxvBeo9hik+++TY/-Tmp-/scan-build-2011-04-05-1'.
xcodebuild: Error: the directory /Users/hudson/work/workspace/My Job does not contain an Xcode project.

          [JENKINS-9251] reports 0 bugs if workspace path contains spaces

          Marcus Better added a comment -

          Correction: only the output above looks weird with the forward slashes. It seems to run scan-build correctly despite this. So it looks more like a visual bug. (I was confused by an unrelated config error.)

          Marcus Better added a comment - Correction: only the output above looks weird with the forward slashes. It seems to run scan-build correctly despite this. So it looks more like a visual bug. (I was confused by an unrelated config error.)

          Marcus Better added a comment -

          Nope, actually the report is correct. I changed my build to use an alternate workspace location without spaces in it, and then the errors get displayed correctly in the graph. Before the change, it reported 0 errors (though the console output indicated that scan-build still found 40 errors).

          Marcus Better added a comment - Nope, actually the report is correct. I changed my build to use an alternate workspace location without spaces in it, and then the errors get displayed correctly in the graph. Before the change, it reported 0 errors (though the console output indicated that scan-build still found 40 errors).

          Josh Kennedy added a comment -

          Release 1.3.1 includes a change to the build to convert the clang tool installation to a node specific tool installation. This resolved the issue of ignoring overriden clang paths on slaves. Masters can now define a scan-build installation and leave the path blank.

          Josh Kennedy added a comment - Release 1.3.1 includes a change to the build to convert the clang tool installation to a node specific tool installation. This resolved the issue of ignoring overriden clang paths on slaves. Masters can now define a scan-build installation and leave the path blank.

            jkennedy1980 Josh Kennedy
            mbetter Marcus Better
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: