[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build

[m.ro...@itc-ag.com (JIRA)]

Title: Message Title

Marco Rothe created an issue   Jenkins / JENKINS-55390 No issues found when parsing Error-Prone output from console log during maven build Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-03 12:45 Environment: Jenkins: 2.156 warnings-ng-plugin: 1.0.1 ecj: 3.16.0, 3.15.1 plexus-compiler: 2.8.5 maven: 3.6.0 java: 1.8.0_191 Priority: Minor Reporter: Marco Rothe Maven build using ECJ completes with: channel stopped [Eclipse ECJ] Sleeping for 5 seconds due to JENKINS-32191... [Eclipse ECJ] Parsing console log (workspace: '/home/jenkins-agent/agent-1/workspace/xxx') [Eclipse ECJ] Attaching ResultAction with ID 'eclipse' to run 'xxx #10'. [Eclipse ECJ] Using reference build 'xxx #9' to compute new, fixed, and outstanding issues [Eclipse ECJ] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0 [Eclipse ECJ] No quality gates have been set - skipping [Eclipse ECJ] Health report is disabled - skipping [Eclipse ECJ] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues) Finished: SUCCESS Parser - indeed has ANT_ECLIPSE_WARNING_PATTERN in EclipseParser.java, not MAVEN in name, yet Documentation promises Maven Project to be supported type. Inspection of job's log with less shows colorised entries with control sequences like below: ESC[8mha:////4ABzfsCHJFyEqbHt1tyu83RhpB1NXTka2OpStZBOt27/AACAYx+LCAAcAWZAAP9ba5aBtbi1QSWjNKU4P0+vJLE4u1gvPjexLDVPzxdEhicW5WXmpfvWl6S2eNly5fzGzaurGBgqihikoFqS8/OK83NS9ZwhlkghAwQwghQWAA14xA+XYgAbAA==ESC[0m[WARNING] /home/jenkins-agent/agent-1/workspace/xxx/.../Y.java:[167,6363] Unqualified access to the field Y.w but I don't know if they are also transferred to ReportScanningTool. If project is executed with modified plexus-compiler (as the currently released one does not support specifying log file plexus-compiler#55) - with log files preserved and fed to warnings-ng - the same build results in ... channel stopped [Eclipse ECJ] Searching for all files in '/home/jenkins-agent/agent-2/workspace/xxx' that match the pattern '**/target/ecjerr-*.xml' [Eclipse ECJ] -> found 10 files [Eclipse ECJ] Successfully parsed file /home/jenkins-agent/agent-2/workspace/xxx/target/ecjerr-1737547503980039210.xml [Eclipse ECJ] -> found 7 issues (skipped 0 duplicates) ... [Eclipse ECJ] Post processing issues on 'phobos-agent-2' with encoding 'UTF-8' [Eclipse ECJ] Resolving absolute file names for all issues [Eclipse ECJ] -> 0 resolved, 0 unresolved, 55 already resolved [Eclipse ECJ] Copying affected files to Jenkins' build folder /home/yyy/.jenkins/jobs/xxx/builds/11 [Eclipse ECJ] -> 55 copied, 0 not in workspace, 0 not-found, 0 with I/O error [Eclipse ECJ] Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files) [Eclipse ECJ] -> resolved module names for 381 issues [Eclipse ECJ] Resolving package names (or namespaces) by parsing the affected files [Eclipse ECJ] -> resolved package names of 55 affected files [Eclipse ECJ] No filter has been set, publishing all 381 issues [Eclipse ECJ] Creating fingerprints for all affected code blocks to track issues over different builds [Eclipse ECJ] -> created fingerprints for 381 issues [Eclipse ECJ] Invoking Git blamer to create author and commit information for all affected files [Eclipse ECJ] GIT_COMMIT env = 'c23f454408747cd7c6158a69c2457c9c98154254' [Eclipse ECJ] Git working tree = '/home/jenkins-agent/agent-2/workspace/xxx' [Eclipse ECJ] Git commit ID = 'c23f454408747cd7c6158a69c2457c9c98154254' [Eclipse ECJ] Job workspace = '/home/jenkins-agent/agent-2/workspace/xxx' [Eclipse ECJ] Created blame requests for 55 files - invoking Git blame on agent for each of the requests [Eclipse ECJ] -> blamed authors of issues in 55 files [Eclipse ECJ] Attaching ResultAction with ID 'eclipse' to run 'xxx #11'. [Eclipse ECJ] Using reference build 'xxx #10' to compute new, fixed, and outstanding issues [Eclipse ECJ] Issues delta (vs. reference build): outstanding: 0, new: 381, fixed: 0 [Eclipse ECJ] No quality gates have been set - skipping [Eclipse ECJ] Health report is disabled - skipping [Eclipse ECJ] Created analysis result for 381 issues (found 381 new issues, fixed 0 issues) Finished: SUCCESS which proves that EclipseXMLParser is really fine.   Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.