SpotBugs - Messages
Information Messages
Searching for all files in '/home/jenkins/agent/workspace/mail-api-build' that match the pattern '**/spotbugsXml.xml'Traversing of symbolic links: enabled-> found 1 fileSuccessfully parsed file /home/jenkins/agent/workspace/mail-api-build/api/target/spotbugsXml.xml-> found 63 issues (skipped 0 duplicates)Successfully processed file 'api/target/spotbugsXml.xml'Post processing issues on 'basic-g59qq' 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 '/home/jenkins/agent/workspace/mail-api-build'-> resolved paths in source directory (27 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 63 issuesCreating fingerprints for all affected code blocks to track issues over different builds-> created fingerprints for 0 issues (skipped 63 issues)Searching for all files in '/home/jenkins/agent/workspace/mail-api-build' that match the pattern '**/spotbugsXml.xml'Traversing of symbolic links: enabled-> found 1 fileSuccessfully parsed file /home/jenkins/agent/workspace/mail-api-build/api/target/spotbugsXml.xml-> found 63 issues (skipped 0 duplicates)Successfully processed file 'api/target/spotbugsXml.xml'Post processing issues on 'basic-g59qq' 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 '/home/jenkins/agent/workspace/mail-api-build'-> resolved paths in source directory (27 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 63 issuesCreating fingerprints for all affected code blocks to track issues over different builds-> created fingerprints for 0 issues (skipped 63 issues)Copying affected files to Jenkins' build folder '/var/jenkins/jobs/mail-api-build/builds/58/files-with-issues'-> 26 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 (mail-api-build)Using reference build 'mail-api-build #57' to compute new, fixed, and outstanding issuesIssues delta (vs. reference build): outstanding: 63, new: 0, fixed: 0No quality gates have been set - skippingHealth report is disabled - skippingCreated analysis result for 63 issues (found 0 new issues, fixed 0 issues)Attaching ResultAction with ID 'spotbugs' to build 'mail-api-build #58'.