-
Bug
-
Resolution: Cannot Reproduce
-
Minor
-
None
-
Jenkins: 2.156
warnings-ng-plugin: 1.0.1
error-prone: 2.3.2
plexus-compiler: 2.8.4
maven: 3.5.4
java: 1.8.0_191
Maven build using Error Prone compiler completes with:
channel stopped [Error Prone] Sleeping for 5 seconds due to JENKINS-32191... [Error Prone] Parsing console log (workspace: '/pathtoworkspace/workspace/xxx') [Error Prone] Attaching ResultAction with ID 'error-prone' to run 'xxx #1411'. [Error Prone] Using reference build 'xxx #1410' to compute new, fixed, and outstanding issues [Error Prone] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0 [Error Prone] Evaluating quality gates [Error Prone] -> All quality gates have been passed [Error Prone] Health report is disabled - skipping [Error Prone] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues) Finished: SUCCESS
Inspection of job's log shows entries like the example below:
[pool-1-thread-3 for channel id=36910] WARNING org.apache.maven.plugin.compiler.CompilerMojo - /pathtoworkspace/workspace/xxx/xxx-module/src/main/java/a/path/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations. (see https://errorprone.info/bugpattern/DefaultCharset) Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?
It seems that the warnings are not detected (due to the 'pool-1-thread' or 'org.apache.maven.plugin.compiler.CompilerMojo' stuff?) from console log.
A local build (using the same maven, java and error-prone version) show the warning in the form below:
[WARNING] <pathtoworkspace>/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations. (see https://errorprone.info/bugpattern/DefaultCharset) Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?
So there is obviously a difference in console-log formating.
- is related to
-
JENKINS-72976 Extra logging added to console log on Maven builds and prevent Error-Prone parsing
- Closed