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

Not possible to set report directory used by Clang-Scan publisher

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • clang-scanbuild-plugin
    • None
    • Jenkins 1.524
      Clang Scan-Build Plugin 1.4

      The Clang-Scan publisher looks for its reports in a hardcoded directory ($WORKSPACE/clangScanBuildReports). I have a requirement that all generated artifacts (including the report from scan-build) be created in a top-level build directory. Please make the publisher configurable to be able to specify the location or the reports (having it default to $WORKSPACE/clangScanBuildReports is perfectly reasonable).

          [JENKINS-18941] Not possible to set report directory used by Clang-Scan publisher

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Maarten Los
          Path:
          src/main/java/jenkins/plugins/clangscanbuild/ClangScanBuildBuilder.java
          src/main/java/jenkins/plugins/clangscanbuild/ClangScanBuildUtils.java
          src/main/java/jenkins/plugins/clangscanbuild/actions/ClangScanBuildAction.java
          src/main/java/jenkins/plugins/clangscanbuild/publisher/ClangScanBuildPublisher.java
          src/main/java/jenkins/plugins/clangscanbuild/publisher/ClangScanBuildPublisherDescriptor.java
          src/main/resources/jenkins/plugins/clangscanbuild/ClangScanBuildBuilder/config.jelly
          src/main/resources/jenkins/plugins/clangscanbuild/publisher/ClangScanBuildPublisher/config.jelly
          src/test/java/jenkins/plugins/clangscanbuild/ClangScanBuildBuilderTest.java
          src/test/java/jenkins/plugins/clangscanbuild/history/ClangScanBuildHistoryGathererImplTest.java
          src/test/java/jenkins/plugins/clangscanbuild/publisher/ClangScanBuildPublisherTest.java
          http://jenkins-ci.org/commit/clang-scanbuild-plugin/b6ceff9b1e7969cf4c830098cbc9ba06df13dab4
          Log:
          JENKINS-18941 Support configuration of output folder in Builder and report folder in Publisher

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Maarten Los Path: src/main/java/jenkins/plugins/clangscanbuild/ClangScanBuildBuilder.java src/main/java/jenkins/plugins/clangscanbuild/ClangScanBuildUtils.java src/main/java/jenkins/plugins/clangscanbuild/actions/ClangScanBuildAction.java src/main/java/jenkins/plugins/clangscanbuild/publisher/ClangScanBuildPublisher.java src/main/java/jenkins/plugins/clangscanbuild/publisher/ClangScanBuildPublisherDescriptor.java src/main/resources/jenkins/plugins/clangscanbuild/ClangScanBuildBuilder/config.jelly src/main/resources/jenkins/plugins/clangscanbuild/publisher/ClangScanBuildPublisher/config.jelly src/test/java/jenkins/plugins/clangscanbuild/ClangScanBuildBuilderTest.java src/test/java/jenkins/plugins/clangscanbuild/history/ClangScanBuildHistoryGathererImplTest.java src/test/java/jenkins/plugins/clangscanbuild/publisher/ClangScanBuildPublisherTest.java http://jenkins-ci.org/commit/clang-scanbuild-plugin/b6ceff9b1e7969cf4c830098cbc9ba06df13dab4 Log: JENKINS-18941 Support configuration of output folder in Builder and report folder in Publisher

            jkennedy1980 Josh Kennedy
            bbassett Brian Bassett
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: