Krzesmir Florek created JENKINS-13311:
-----------------------------------------
Summary: Log Parser Plugin ignores sonar logs
Key: JENKINS-13311
URL: https://issues.jenkins-ci.org/browse/JENKINS-13311
Project: Jenkins
Issue Type: Improvement
Components: log-parser
Reporter: Krzesmir Florek
Assignee: rgoren
In case of a jenkins job with sonar analysis enabled, the log parser parses
only the main part of the build and ignores the rest, so there is no possiblity
of parsing sonar's output.
example:
- console
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 20 seconds
[INFO] Finished at: Mon Apr 02 11:48:29 CEST 2012
[INFO] Final Memory: 32M/292M
[INFO] ------------------------------------------------------------------------
[TASKS] Aggregating results of XXX
[TASKS] Using set difference to compute new warnings
[TASKS] Not changing build status, since no threshold has been exceeded
channel stopped
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
[trunk] $ /opt/maven/2.2.1/bin/mvn ...
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'sonar'.
...
-parsed console
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 20 seconds
[INFO] Finished at: Mon Apr 02 11:48:29 CEST 2012
[INFO] Final Memory: 32M/292M
[INFO] ------------------------------------------------------------------------
[TASKS] Aggregating results of XXX
[TASKS] Using set difference to compute new warnings
[TASKS] Not changing build status, since no threshold has been exceeded
channel stopped
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
