AspectJ - Messages
Information Messages
Successfully parsed console log-> found 2 issues (skipped 17 duplicates)Successfully parsed console log-> found 2 issues (skipped 17 duplicates)Successfully parsed console log-> found 2 issues (skipped 17 duplicates)Successfully parsed console log-> found 2 issues (skipped 17 duplicates)Parsing console log (workspace: '/var/jenkins_home/jobs/blueHour_Metrics/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/workspace'-> none of the issues requires resolving of pathsResolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)-> resolved module names for 2 issuesResolving package names (or namespaces) by parsing the affected files-> resolved package names of 1 affected filesNo filter has been set, publishing all 2 issuesCreating fingerprints for all affected code blocks to track issues over different builds-> created fingerprints for 0 issues (skipped 2 issues)Copying affected files to Jenkins' build folder '/var/jenkins_home/jobs/blueHour_Metrics/builds/1314/files-with-issues'-> 0 copied, 0 not in workspace, 2 not-found, 0 with I/O errorRepository miner is not configured, skipping repository miningReference build recorder is not configuredObtaining reference build from same job (blueHour :: Metrics)Using reference build 'blueHour_Metrics #1313' to compute new, fixed, and outstanding issuesIssues delta (vs. reference build): outstanding: 2, new: 0, fixed: 0No quality gates have been set - skippingHealth report is disabled - skippingCreated analysis result for 2 issues (found 0 new issues, fixed 0 issues)Attaching ResultAction with ID 'aspectj' to build 'blueHour_Metrics #1314'.