[
http://jira.codehaus.org/browse/MFITNESSE-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Andersen closed MFITNESSE-17.
---------------------------------
Resolution: Fixed
The feedback from Jetbrains to patch the mvn.bat does the trick!
> build status reported as [ERROR] but should be [FAILURE] if a FitNesse test
> fails
> ---------------------------------------------------------------------------------
>
> Key: MFITNESSE-17
> URL: http://jira.codehaus.org/browse/MFITNESSE-17
> Project: Maven 2.x Fitnesse Plugin
> Issue Type: Bug
> Environment: fitnesse-maven-plugin 1.0-beta-2-SNAPSHOT, TeamCity
> Version 2.1.1(build 4261), Maven 2.0.7
> Reporter: Tim Andersen
> Assignee: pkernevez
> Attachments: JUnit error.jpg, teamcity-build-status.jpg
>
>
> We use TeamCity for continuous integration. When a FitNesse test fails using
> the fitnesse-maven-plugin it does not fail the build. The build status
> should be changed to [FAILURE] instead of [ERROR] to fail the build if a
> FitNesse test fails.
> Alternatively, the fitnesse-maven-plugin should generate a teamcity-info.xml
> so TeamCity knows to fail the build if one of the FitNesse tests fail.
> Here is JetBrains link on how to include Third-Party Reports in the Build
> Results
> http://www.jetbrains.net/confluence/display/TCD3/Including+Third-Party+Reports+in+the+Build+Results
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
