hhuynh commented on Bug JENKINS-15324

Here's the console log of a failure build triggered by new findbug error (not a typical compile/test error). My previous build had 103 warnings. This run has 104 warnings hence the build failed.

[INFO] — findbugs-maven-plugin:2.4.0:findbugs (default-cli) @ ehcache-core —
[INFO] Fork Value is true
[java] The following classes needed for analysis were missing:
[java] org.osgi.framework.BundleActivator
[java] Warnings generated: 104
[java] Missing classes: 1
[INFO] Done FindBugs Analysis....
mojoSucceeded org.codehaus.mojo:findbugs-maven-plugin:2.4.0(default-cli)
[FINDBUGS] Finding all files that match the pattern findbugsXml.xml
[FINDBUGS] Parsing 1 files in h:\jenkins\jobs\mavenjob\workspace\target
[FINDBUGS] Successfully parsed file h:\jenkins\jobs\mavenjob\workspace\target\findbugsXml.xml of module ehcache-core with 104 warnings.
[FINDBUGS] Computing warning deltas based on reference build #1
projectSucceeded net.sf.ehcache.internal:ehcache-core:2.7.0-SNAPSHOT
sessionEnded
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 43.220s
[INFO] Finished at: Thu Sep 27 09:34:04 PDT 2012
[INFO] Final Memory: 25M/94M
[INFO] ------------------------------------------------------------------------
Projects to build: [MavenProject: net.sf.ehcache.internal:ehcache-core:2.7.0-SNAPSHOT @ h:\jenkins\jobs\mavenjob\workspace\pom.xml]
[JENKINS] Archiving h:\jenkins\jobs\mavenjob\workspace\pom.xml to h:\jenkins\jobs\mavenjob\modules\net.sf.ehcache.internal$ehcache-core\builds\2012-09-27_09-33-19\archive\net.sf.ehcache.internal\ehcache-core\2.7.0-SNAPSHOT\ehcache-core-2.7.0-SNAPSHOT.pom
Waiting for Jenkins to finish collecting data
channel stopped
[ANALYSIS-COLLECTOR] Skipping publisher since build result is FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to