CPD - Messages

Searching for all files in '/var/jenkins_home/jobs/TheseFoolishThings_Metrics_branches/workspace' that match the pattern '**/cpd.xml'
Traversing of symbolic links: enabled
-> found 1 file
Successfully parsed file /var/jenkins_home/jobs/TheseFoolishThings_Metrics_branches/workspace/target/cpd.xml
-> found 2 issues (skipped 0 duplicates)
Successfully processed file 'target/cpd.xml'
Post processing issues on 'Master' with source code encoding 'UTF-8'
Creating SCM blamer to obtain author and commit information for affected files
-> No blamer installed yet. You need to install the 'git-forensics' plugin to enable blaming for Git.
Resolving file names for all issues in workspace '/var/jenkins_home/jobs/TheseFoolishThings_Metrics_branches/workspace'
-> resolved paths in source directory (2 found, 0 not found)
Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
-> resolved module names for 2 issues
Resolving package names (or namespaces) by parsing the affected files
-> resolved package names of 2 affected files
No filter has been set, publishing all 2 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 2 issues (skipped 0 issues)
Searching for all files in '/var/jenkins_home/jobs/TheseFoolishThings_Metrics_branches/workspace' that match the pattern '**/cpd.xml'
Traversing of symbolic links: enabled
-> found 1 file
Successfully parsed file /var/jenkins_home/jobs/TheseFoolishThings_Metrics_branches/workspace/target/cpd.xml
-> found 2 issues (skipped 0 duplicates)
Successfully processed file 'target/cpd.xml'
Post processing issues on 'Master' with source code encoding 'UTF-8'
Creating SCM blamer to obtain author and commit information for affected files
-> No blamer installed yet. You need to install the 'git-forensics' plugin to enable blaming for Git.
Resolving file names for all issues in workspace '/var/jenkins_home/jobs/TheseFoolishThings_Metrics_branches/workspace'
-> resolved paths in source directory (2 found, 0 not found)
Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
-> resolved module names for 2 issues
Resolving package names (or namespaces) by parsing the affected files
-> resolved package names of 2 affected files
No filter has been set, publishing all 2 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 2 issues (skipped 0 issues)
Copying affected files to Jenkins' build folder '/var/jenkins_home/jobs/TheseFoolishThings_Metrics_branches/builds/16/files-with-issues'
-> 0 copied, 0 not in workspace, 0 not-found, 0 with I/O error
Repository miner is not configured, skipping repository mining
Reference build recorder is not configured
Obtaining reference build from same job (TheseFoolishThings :: Metrics (feature branches))
Using reference build 'TheseFoolishThings_Metrics_branches #15' to compute new, fixed, and outstanding issues
Issues delta (vs. reference build): outstanding: 0, new: 2, fixed: 0
No quality gates have been set - skipping
Health report is disabled - skipping
Created analysis result for 2 issues (found 2 new issues, fixed 0 issues)
Attaching ResultAction with ID 'cpd' to build 'TheseFoolishThings_Metrics_branches #16'.