Open Tasks Scanner - Messages
Information Messages
Searching for files in workspace '/var/jenkins_home/jobs/blueMarine2/workspace' that match the include pattern '' and exclude pattern ''-> found 19259 files that will be scannedUsing the following tasks patterns: -> High: ^.*(\bFIXME\b)(.*)$ -> Normal: ^.*(\bTODO\b)(.*)$Scanning all 19259 files for open tasksFound a total of 1484 open tasks-> FIXME: 816 open tasks-> TODO: 668 open tasksPost 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/blueMarine2/workspace'-> resolved paths in source directory (534 found, 0 not found)Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)-> resolved module names for 1484 issuesResolving package names (or namespaces) by parsing the affected files-> resolved package names of 534 affected filesNo filter has been set, publishing all 1484 issuesCreating fingerprints for all affected code blocks to track issues over different builds-> created fingerprints for 1484 issues (skipped 0 issues)Searching for files in workspace '/var/jenkins_home/jobs/blueMarine2/workspace' that match the include pattern '' and exclude pattern ''-> found 19259 files that will be scannedUsing the following tasks patterns: -> High: ^.*(\bFIXME\b)(.*)$ -> Normal: ^.*(\bTODO\b)(.*)$Scanning all 19259 files for open tasksFound a total of 1484 open tasks-> FIXME: 816 open tasks-> TODO: 668 open tasksPost 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/blueMarine2/workspace'-> resolved paths in source directory (534 found, 0 not found)Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)-> resolved module names for 1484 issuesResolving package names (or namespaces) by parsing the affected files-> resolved package names of 534 affected filesNo filter has been set, publishing all 1484 issuesCreating fingerprints for all affected code blocks to track issues over different builds-> created fingerprints for 1484 issues (skipped 0 issues)Copying affected files to Jenkins' build folder '/var/jenkins_home/jobs/blueMarine2/builds/357/files-with-issues'-> 534 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 (blueMarine2 :: Archive)Using reference build 'blueMarine2 #356' to compute new, fixed, and outstanding issuesIssues delta (vs. reference build): outstanding: 1479, new: 5, fixed: 5No quality gates have been set - skippingHealth report is disabled - skippingCreated analysis result for 1484 issues (found 5 new issues, fixed 5 issues)Attaching ResultAction with ID 'open-tasks' to build 'blueMarine2 #357'.