Unable to resolve file names when command is part of Dockerfile execution

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Hi drulli sorry to bother you, I don't know if this a bug or what is going on.

      I have following step in my pipeline

       

              always
      {             recordIssues enabledForFailure: true, tool: gcc(), sourceDirectory: './Source'         }
      

       

      Unfortunately, the plugin is unable to find my source files. I've tried pass sourceDirectory as relative and full paths.

      I am also sure that the source files are there:

       

      jenkins@0bbdc0cab2a7:~$ ls /var/jenkins_home/workspace/cpp-ci-demo_main/Source/
      Functions.cpp  Functions.hpp  Main.cpp    Tests.cpp

       

       

      And here is the full log.

       

      [GNU C Compiler (gcc)] Post processing issues on 'Master' with source code encoding 'UTF-8'
      [GNU C Compiler (gcc)] Creating SCM blamer to obtain author and commit information for affected files
      [GNU C Compiler (gcc)] -> Git blamer successfully created in working tree '/var/jenkins_home/workspace/cpp-ci-demo_main'
      [GNU C Compiler (gcc)] Resolving file names for all issues in workspace '/var/jenkins_home/workspace/cpp-ci-demo_main'
      [GNU C Compiler (gcc)] -> resolved paths in source directory (0 found, 1 not found)
      [GNU C Compiler (gcc)] Resolving file names for all issues in source directory '/var/jenkins_home/workspace/cpp-ci-demo_main/Source'
      [GNU C Compiler (gcc)] -> resolved paths in source directory (0 found, 1 not found)
      [GNU C Compiler (gcc)] Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
      [GNU C Compiler (gcc)] -> resolved module names for 1 issues
      [GNU C Compiler (gcc)] Resolving package names (or namespaces) by parsing the affected files
      [GNU C Compiler (gcc)] -> resolved package names of 1 affected files
      [GNU C Compiler (gcc)] No filter has been set, publishing all 1 issues
      [GNU C Compiler (gcc)] Creating fingerprints for all affected code blocks to track issues over different builds
      [GNU C Compiler (gcc)] -> created fingerprints for 0 issues (skipped 1 issues)
      [GNU C Compiler (gcc)] Invoking Git blamer to create author and commit information for 1 affected files
      [GNU C Compiler (gcc)] -> GIT_COMMIT env = 'HEAD'
      [GNU C Compiler (gcc)] -> Git commit ID = '2fce8a593d3362537ade47fb9185947a7dc1cafd'
      [GNU C Compiler (gcc)] -> Git working tree = '/var/jenkins_home/workspace/cpp-ci-demo_main'
      [GNU C Compiler (gcc)] -> blamed authors of issues in 0 files
      [GNU C Compiler (gcc)] Blaming of authors took 1 seconds
      [GNU C Compiler (gcc)] Copying affected files to Jenkins' build folder '/var/jenkins_home/jobs/cpp-ci-demo/branches/main/builds/74/files-with-issues'
      [GNU C Compiler (gcc)] -> 0 copied, 0 not in workspace, 1 not-found, 0 with I/O error
      [GNU C Compiler (gcc)] Repository miner is not configured, skipping repository mining
      [GNU C Compiler (gcc)] [-ERROR-] Can't create fingerprints for some files:
      [GNU C Compiler (gcc)] [-ERROR-] - '/usr/cpp-ci-demo/build/#11 2.148 /usr/cpp-ci-demo/Source/Tests.cpp' file not found
      [GNU C Compiler (gcc)] Parsing console log (workspace: '/var/jenkins_home/workspace/cpp-ci-demo_main')
      [GNU C Compiler (gcc)] Successfully parsed console log
      [GNU C Compiler (gcc)] -> found 1 issue (skipped 0 duplicates)
      [GNU C Compiler (gcc)] Post processing issues on 'Master' with source code encoding 'UTF-8'
      [GNU C Compiler (gcc)] Creating SCM blamer to obtain author and commit information for affected files
      [GNU C Compiler (gcc)] -> Git blamer successfully created in working tree '/var/jenkins_home/workspace/cpp-ci-demo_main'
      [GNU C Compiler (gcc)] Resolving file names for all issues in workspace '/var/jenkins_home/workspace/cpp-ci-demo_main'
      [GNU C Compiler (gcc)] -> resolved paths in source directory (0 found, 1 not found)
      [GNU C Compiler (gcc)] Resolving file names for all issues in source directory '/var/jenkins_home/workspace/cpp-ci-demo_main/Source'
      [GNU C Compiler (gcc)] -> resolved paths in source directory (0 found, 1 not found)
      [GNU C Compiler (gcc)] Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
      [GNU C Compiler (gcc)] -> resolved module names for 1 issues
      [GNU C Compiler (gcc)] Resolving package names (or namespaces) by parsing the affected files
      [GNU C Compiler (gcc)] -> resolved package names of 1 affected files
      [GNU C Compiler (gcc)] No filter has been set, publishing all 1 issues
      [GNU C Compiler (gcc)] Creating fingerprints for all affected code blocks to track issues over different builds
      [GNU C Compiler (gcc)] -> created fingerprints for 0 issues (skipped 1 issues)
      [GNU C Compiler (gcc)] Invoking Git blamer to create author and commit information for 1 affected files
      [GNU C Compiler (gcc)] -> GIT_COMMIT env = 'HEAD'
      [GNU C Compiler (gcc)] -> Git commit ID = '2fce8a593d3362537ade47fb9185947a7dc1cafd'
      [GNU C Compiler (gcc)] -> Git working tree = '/var/jenkins_home/workspace/cpp-ci-demo_main'
      [GNU C Compiler (gcc)] -> blamed authors of issues in 0 files
      [GNU C Compiler (gcc)] Blaming of authors took 1 seconds
      [GNU C Compiler (gcc)] Copying affected files to Jenkins' build folder '/var/jenkins_home/jobs/cpp-ci-demo/branches/main/builds/74/files-with-issues'
      [GNU C Compiler (gcc)] -> 0 copied, 0 not in workspace, 1 not-found, 0 with I/O error
      [GNU C Compiler (gcc)] Repository miner is not configured, skipping repository mining
      [GNU C Compiler (gcc)] [-ERROR-] Can't create fingerprints for some files:
      [GNU C Compiler (gcc)] [-ERROR-] - '/usr/cpp-ci-demo/build/#11 2.148 /usr/cpp-ci-demo/Source/Tests.cpp' file not found
      [GNU C Compiler (gcc)] Reference build recorder is not configured
      [GNU C Compiler (gcc)] Obtaining reference build from same job (main)
      [GNU C Compiler (gcc)] Using reference build 'cpp-ci-demo/main #73' to compute new, fixed, and outstanding issues
      [GNU C Compiler (gcc)] Issues delta (vs. reference build): outstanding: 0, new: 1, fixed: 0
      [GNU C Compiler (gcc)] No quality gates have been set - skipping
      [GNU C Compiler (gcc)] Health report is disabled - skipping
      [GNU C Compiler (gcc)] Created analysis result for 1 issues (found 1 new issues, fixed 0 issues)
      [GNU C Compiler (gcc)] Attaching ResultAction with ID 'gcc' to build 'cpp-ci-demo/main #74'.
      [Checks API] No suitable checks publisher found.

      Thanks for any help.

            Assignee:
            Unassigned
            Reporter:
            Marcin Czernow
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: