sonar-pom.xml cannot be written at workspace root directory

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Critical
    • Component/s: sonar-plugin
    • None
    • Environment:
      Platform: All, OS: All

      When Hudson uses a dynamic ClearCase View, the workspace root directory is
      M:/myView or /view/MyView: it is a directly managed by MVFS
      (http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg21230196), meaning the
      root directory is read-only.

      Hence the following stack-trace

      Building on master
      [swfged_plenita_aex_jrk_int_dyn] $ cleartool pwv -root
      /view/swfged_plenita_aex_jrk_int_dyn
      [workspace] $ cleartool startview swfged_plenita_aex_jrk_int_dyn
      [workspace] $ cleartool setcs -tag swfged_plenita_aex_jrk_int_dyn -stream
      [swfged_plenita_aex_jrk_int_dyn] $ cleartool lshistory -all -since
      20-nov-09.09:26:29utc+0000 -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\"
      \"%[activity]p\" \n%c\n' -branch brtype:AEX_JRK_Int -nco vobs/framework/aex_jrk
      FATAL: command execution failed
      java.io.FileNotFoundException:
      /view/swfged_plenita_aex_jrk_int_dyn/sonar-pom.xml (Permission denied)
      at java.io.FileOutputStream.open(Native Method)
      at java.io.FileOutputStream.<init>(FileOutputStream.java:209)
      at java.io.FileOutputStream.<init>(FileOutputStream.java:160)
      at hudson.FilePath$25.call(FilePath.java:1180)
      at hudson.FilePath$25.call(FilePath.java:1176)
      at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
      at hudson.FilePath.write(FilePath.java:1176)
      at hudson.plugins.sonar.template.SimpleTemplate.write(SimpleTemplate.java:62)
      at
      hudson.plugins.sonar.SonarPublisher.generatePomForNonMavenProject(SonarPublisher.java:331)
      at hudson.plugins.sonar.SonarPublisher.executeSonar(SonarPublisher.java:284)
      at hudson.plugins.sonar.SonarPublisher.perform(SonarPublisher.java:243)
      at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)

      Solution: add a field allowing to define the relative path where sonar-pom.xml
      is written. By default, keep the current path (i.e. the root directory of the
      workspace)

            Assignee:
            Sonar Team
            Reporter:
            sgidea
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: