SpotBugs - Messages
Information Messages
Searching for all files in '/var/jenkins_home/jobs/SolidBlue3_Metrics_branches/workspace' that match the pattern '**/target/**/findbugsXml.xml,**/target/**/spotbugsXml.xml'Traversing of symbolic links: enabled-> found 4 filesSuccessfully parsed file /var/jenkins_home/jobs/SolidBlue3_Metrics_branches/workspace/modules/Application/target/site/spotbugsXml.xml-> found 0 issues (skipped 0 duplicates)Successfully processed file 'modules/Application/target/site/spotbugsXml.xml'Successfully parsed file /var/jenkins_home/jobs/SolidBlue3_Metrics_branches/workspace/modules/Commons/target/site/spotbugsXml.xml-> found 0 issues (skipped 0 duplicates)Successfully processed file 'modules/Commons/target/site/spotbugsXml.xml'Successfully parsed file /var/jenkins_home/jobs/SolidBlue3_Metrics_branches/workspace/modules/Dao/target/site/spotbugsXml.xml-> found 1 issue (skipped 0 duplicates)Successfully processed file 'modules/Dao/target/site/spotbugsXml.xml'Successfully parsed file /var/jenkins_home/jobs/SolidBlue3_Metrics_branches/workspace/modules/Model/target/site/spotbugsXml.xml-> found 0 issues (skipped 0 duplicates)Successfully processed file 'modules/Model/target/site/spotbugsXml.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/SolidBlue3_Metrics_branches/workspace'-> resolved paths in source directory (1 found, 0 not found)Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)-> all issues already have a valid module nameResolving package names (or namespaces) by parsing the affected files-> all affected files already have a valid package nameNo filter has been set, publishing all 1 issuesCreating fingerprints for all affected code blocks to track issues over different builds-> created fingerprints for 0 issues (skipped 1 issues)Copying affected files to Jenkins' build folder '/var/jenkins_home/jobs/SolidBlue3_Metrics_branches/builds/192/files-with-issues'-> 1 copied, 0 not in workspace, 0 not-found, 0 with I/O errorRepository miner is not configured, skipping repository miningReference build recorder is not configuredObtaining reference build from same job (SolidBlue3 :: Metrics (feature branches))Using reference build 'SolidBlue3_Metrics_branches #191' to compute new, fixed, and outstanding issuesIssues delta (vs. reference build): outstanding: 1, new: 0, fixed: 0No quality gates have been set - skippingHealth report is disabled - skippingCreated analysis result for 1 issues (found 0 new issues, fixed 0 issues)Attaching ResultAction with ID 'spotbugs' to build 'SolidBlue3_Metrics_branches #192'.