also.. i realized that apparently things like compilation failures or download maven artifact failures only shows in the build logs..
That's strange. Compilation errors should be shown on the build results page. Downloading maven artifact failure is pretty specific, so I think it's ok to show it on the build log.
That's strange. Compilation errors should be shown on the build results page.
Should they? This is how the results page looks like if a compile fails within Maven: To see the "real" compiler message I always have to switch to "All messages". The output below is in brown/orange color.
Maven2 output: Uploading: file://s:/Projekte/Milano/Maven/de/zeiss/milano/common/MilanoCommon/0.0.1-SNAPSHOT/MilanoCommon-0.0.1-20061108.145555-105.jar 55K uploaded Compiling 153 source files to C:\BuildAgent\work\Milano_Common\ZeissTouchscreen\target\classes org.apache.maven.reactor.MavenExecutionException: Compilation failure at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:174) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:689) at jetbrains.maven.Maven21Launcher.executeMaven(Maven21Launcher.java:116) at jetbrains.maven.Maven21Launcher.main(Maven21Launcher.java:49) Caused by: org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:150) ... 3 more Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:505) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) ... 10 more Number of processed tests: 0
org.apache.maven.reactor.MavenExecutionException: There are test failures. at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:174) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:689) at jetbrains.maven.Maven21Launcher.executeMaven(Maven21Launcher.java:116) at jetbrains.maven.Maven21Launcher.main(Maven21Launcher.java:49) Caused by: org.apache.maven.BuildFailureException: There are test failures. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:150) ... 3 more Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures. at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:403) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) ... 10 more Number of processed tests: 0
On the project page, the build result only says "Failure", I don't even get a hint that it was an unsuccessful test that caused the failure. And even under "Build Log"->"All Messages" there is no way to see which test failed. The IntelliJ plugin says "no failed tests" when I click on the according icon.
Once again my question: How are Maven2 runner build results supposed to look like? Is it expected to get clickable compiler error messages like the Ipr runner produces them? Is it expected to get detailed information which JUnit test cases passed and which didn't (including in the IDEA plugin) like you get the information when using Ipr runner?
I just get a build failure (without differntiating between a compile error, test error or whatever else) and a handful of Maven stacktraces, like I posted above. Is this the expected behaviour or is just something not working correctly here?
Is there better support for Maven builds planned in the near future?
Once again my question: How are Maven2 runner build results supposed to look like? Is it expected to get clickable compiler error messages like the Ipr runner produces them?
I'm afraid, this haven't been implemented for Maven. Please file a feature request for that.
Is it expected to get detailed information which JUnit test cases passed and which didn't (including in the IDEA plugin) like you get the information when using Ipr runner?
Yes, this should work.
I just get a build failure (without differntiating between a compile error, test error or whatever else) and a handful of Maven stacktraces, like I posted above.
There could be some failures caused by neither tests nor compilation. That's why you may need to examine build log to find real source of the problem.
Is this the expected behaviour or is just something not working correctly here?
I cannot say for sure until I see your build logs.
Is there better support for Maven builds planned in the near future?
Not yet. There are some maven-related requests and issues, like
bin zhu wrote:
Hmm. In fact you should see it on the results page.
Otherwise you may investigate "Build Log" in "All messages" mode.
--
Kirill Maximov
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"
how can i get team city to show which tests failed in the email that it sends out like cruisecontrol
also.. i realized that apparently things like compilation failures or download maven artifact failures only shows in the build logs..
thanks for the great product
bin zhu wrote:
You can read about email messages customization at
http://www.jetbrains.net/confluence/display/TW/Notificatortemplatescustomization
That's strange. Compilation errors should be shown on the build results page.
Downloading maven artifact failure is pretty specific, so I think it's ok to show it on the
build log.
Kind regards,
KIR
--
Kirill Maximov
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"
great! i should have searched a bit more
also.. i think in this case the compilation error is also maven 2 specific.. since maven is doing the compilation.. not teamcity
how can i show the files changed?
it seems that tag only show the comment of the checkin
thanks
Message was edited by: bin
bin zhu
Should they?
This is how the results page looks like if a compile fails within Maven:
To see the "real" compiler message I always have to switch to "All messages".
The output below is in brown/orange color.
Maven2 output:
Uploading: file://s:/Projekte/Milano/Maven/de/zeiss/milano/common/MilanoCommon/0.0.1-SNAPSHOT/MilanoCommon-0.0.1-20061108.145555-105.jar
55K uploaded
Compiling 153 source files to C:\BuildAgent\work\Milano_Common\ZeissTouchscreen\target\classes
org.apache.maven.reactor.MavenExecutionException: Compilation failure
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:174)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:689)
at jetbrains.maven.Maven21Launcher.executeMaven(Maven21Launcher.java:116)
at jetbrains.maven.Maven21Launcher.main(Maven21Launcher.java:49)
Caused by: org.apache.maven.BuildFailureException: Compilation failure
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:150)
... 3 more
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:505)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
... 10 more
Number of processed tests: 0
This is how it looks like when a test run by Maven fails:
Maven2 output:
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec
Running de.zeiss.milano.basic.tools.dataaccess.FileSectionsTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running de.zeiss.milano.basic.tools.dataaccess.FileConfigurationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Results :
Tests run: 11, Failures: 1, Errors: 0, Skipped: 0
org.apache.maven.reactor.MavenExecutionException: There are test failures.
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:174)
at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:689)
at jetbrains.maven.Maven21Launcher.executeMaven(Maven21Launcher.java:116)
at jetbrains.maven.Maven21Launcher.main(Maven21Launcher.java:49)
Caused by: org.apache.maven.BuildFailureException: There are test failures.
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:150)
... 3 more
Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures.
at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:403)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
... 10 more
Number of processed tests: 0
On the project page, the build result only says "Failure", I don't even get a hint that it was an unsuccessful test that caused the failure.
And even under "Build Log"->"All Messages" there is no way to see which test failed.
The IntelliJ plugin says "no failed tests" when I click on the according icon.
Once again my question:
How are Maven2 runner build results supposed to look like?
Is it expected to get clickable compiler error messages like the Ipr runner produces them?
Is it expected to get detailed information which JUnit test cases passed and which didn't (including in the IDEA plugin) like you get the information when using Ipr runner?
I just get a build failure (without differntiating between a compile error, test error or whatever else) and a handful of Maven stacktraces, like I posted above.
Is this the expected behaviour or is just something not working correctly here?
Is there better support for Maven builds planned in the near future?
Hi Tobias,
Tobias Kurzke wrote:
I'm afraid, this haven't been implemented for Maven. Please file a feature request for that.
Yes, this should work.
There could be some failures caused by neither tests nor compilation.
That's why you may need to examine build log to find real source of the problem.
I cannot say for sure until I see your build logs.
Not yet. There are some maven-related requests and issues, like
http://www.jetbrains.net/jira/browse/TW-716
http://www.jetbrains.net/jira/browse/TW-715
http://www.jetbrains.net/jira/browse/TW-1049
If you have specific ideas, feel free to contribute.
Kind regards,
KIR
--
Kirill Maximov
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"