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

Can't copy source files from slave to master if security is enabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • warnings-ng-plugin
    • None
    • 5.2.0

      Running the warnings-ng plugin in a pipeline job on a slave, the output is parsed correctly and generates report otuput as expected, but errors are generated because the files-with-issues folder is not created on the master. Other than suspect files not being copied to this folder, the rest of the plugin processes appear to run just fine.

      The pipeline step is 

      recordIssues tools: [msBuild()] 

       

      Log output from Jenkins is:

      [Pipeline] recordIssues
      Skipping issues blame since Git is the only supported SCM up to now.
      [MSBuild] Sleeping for 5 seconds due to JENKINS-32191...
      [MSBuild] Parsing console log (workspace: 'D:\caProjects\workspace\MyProject\eptest')
      [MSBuild] [ERROR] Can't copy some affected workspace files to Jenkins build folder:
      [MSBuild] [ERROR] - 'D:/caProjects/workspace/MyProject/eptest/MyProject.WebService/Startup.cs', IO exception has been thrown: java.io.IOException: Can't create directory for workspace files that contain issues: files-with-issues
      ...I have removed an additional 19 errors identical to above except for filename
      [MSBuild] [ERROR] ... skipped logging of 23 additional errors ...
      [MSBuild] Post processing issues on 'MyProject' with encoding 'windows-1252'
      [MSBuild] Resolving absolute file names for all issues
      [MSBuild] -> 1 resolved, 0 unresolved, 43 already resolved
      [MSBuild] Copying affected files to Jenkins' build folder E:\Jenkins\MyProject\eptest\builds\73
      [MSBuild] -> 0 copied, 1 not in workspace, 0 not-found, 43 with I/O error
      [MSBuild] Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
      [MSBuild] -> resolved module names for 144 issues
      [MSBuild] Resolving package names (or namespaces) by parsing the affected files
      [MSBuild] -> resolved package names of 44 affected files
      [MSBuild] No filter has been set, publishing all 144 issues
      [MSBuild] Creating fingerprints for all affected code blocks to track issues over different builds
      [MSBuild] -> created fingerprints for 144 issues
      [MSBuild] Skipping blaming as requested in the job configuration
      [MSBuild] Attaching ResultAction with ID 'msbuild' to run 'MyProject/eptest #73'.
      [MSBuild] Using reference build 'MyProject/eptest #72' to compute new, fixed, and outstanding issues
      [MSBuild] Issues delta (vs. reference build): outstanding: 144, new: 0, fixed: 0
      [MSBuild] No quality gates have been set - skipping
      [MSBuild] Health report is disabled - skipping
      [MSBuild] Created analysis result for 144 issues (found 0 new issues, fixed 0 issues)

            drulli Ulli Hafner
            markdulfer Mark Dulfer
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: