AspectJ - Messages

Successfully parsed console log
-> found 3 issues (skipped 21 duplicates)
Successfully parsed console log
-> found 3 issues (skipped 21 duplicates)
Successfully parsed console log
-> found 3 issues (skipped 21 duplicates)
Successfully parsed console log
-> found 3 issues (skipped 21 duplicates)
Parsing console log (workspace: '/var/jenkins_home/jobs/blueHour_Metrics_branches/workspace')
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/blueHour_Metrics_branches/workspace'
-> none of the issues requires resolving of paths
Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
-> resolved module names for 3 issues
Resolving package names (or namespaces) by parsing the affected files
-> resolved package names of 1 affected files
No filter has been set, publishing all 3 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 0 issues (skipped 3 issues)
Copying affected files to Jenkins' build folder '/var/jenkins_home/jobs/blueHour_Metrics_branches/builds/6/files-with-issues'
-> 0 copied, 0 not in workspace, 3 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 (blueHour :: Metrics (feature branches))
No valid reference build found that meets the criteria (NO_JOB_FAILURE - SUCCESSFUL_QUALITY_GATE)
All reported issues will be considered outstanding
No quality gates have been set - skipping
Health report is disabled - skipping
Created analysis result for 3 issues (found 0 new issues, fixed 0 issues)
Attaching ResultAction with ID 'aspectj' to build 'blueHour_Metrics_branches #6'.