SpotBugs - Messages

Searching for all files in '/var/lib/jenkins/home/jobs/ipfli4l13/workspace/ipfli4l13' that match the pattern '**/ipfli4l13/reports/spotbugs-*/spotbugs-*.xml'
Traversing of symbolic links: enabled
-> found 1 file
Successfully parsed file /var/lib/jenkins/home/jobs/ipfli4l13/workspace/ipfli4l13/ipfli4l13/reports/spotbugs-3.1.11/spotbugs-3.1.11.xml
-> found 128 issues (skipped 0 duplicates)
Successfully processed file 'ipfli4l13/reports/spotbugs-3.1.11/spotbugs-3.1.11.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/lib/jenkins/home/jobs/ipfli4l13/workspace/ipfli4l13'
-> resolved paths in source directory (57 found, 0 not found)
Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
-> resolved module names for 128 issues
Resolving package names (or namespaces) by parsing the affected files
-> all affected files already have a valid package name
No filter has been set, publishing all 128 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 0 issues (skipped 128 issues)
Ignoring 'aggregatingResults' and ID 'null' since only a single tool is defined.
Searching for all files in '/var/lib/jenkins/home/jobs/ipfli4l13/workspace/ipfli4l13' that match the pattern '**/ipfli4l13/reports/spotbugs-*/spotbugs-*.xml'
Traversing of symbolic links: enabled
-> found 1 file
Successfully parsed file /var/lib/jenkins/home/jobs/ipfli4l13/workspace/ipfli4l13/ipfli4l13/reports/spotbugs-3.1.11/spotbugs-3.1.11.xml
-> found 128 issues (skipped 0 duplicates)
Successfully processed file 'ipfli4l13/reports/spotbugs-3.1.11/spotbugs-3.1.11.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/lib/jenkins/home/jobs/ipfli4l13/workspace/ipfli4l13'
-> resolved paths in source directory (57 found, 0 not found)
Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)
-> resolved module names for 128 issues
Resolving package names (or namespaces) by parsing the affected files
-> all affected files already have a valid package name
No filter has been set, publishing all 128 issues
Creating fingerprints for all affected code blocks to track issues over different builds
-> created fingerprints for 0 issues (skipped 128 issues)
Copying affected files to Jenkins' build folder '/var/lib/jenkins/home/jobs/ipfli4l13/builds/ipfli4l13/1584/files-with-issues'
-> 57 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 (ipfli4l13)
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 128 issues (found 0 new issues, fixed 0 issues)
Attaching ResultAction with ID 'spotbugs' to build 'ipfli4l13 #1584'.