>> What is the point of JUnit failure reports in CI environment? It's absolutely un-acceptable situation when your source codebase contains a defect in "trunk". It's not a matter of reporting any more, but of an immediate action. >> If you still need your build to be valid with defects inside (unit test failures) you should use this surefire configuration option:
I do want to fail the build of course (otherwise broken artifacts would get deployed). And I do want my developers to take immediate action as well of course. But to do so I must inform them about the failure in a convenient way, don't I? Therefore we have a CI system, which sends an email of the broken build. Devs then enter the TeamCity web-page and there I want to present a nice (i.e. HTML) failure report (i.e. the current CheckStyle errors that need to be resolved instantly), to make the build green again. I definitely don't want the developers to scan the build-log to find the lines from Checkstyle there. So right now the only 'working' solution I found, it to create a 'plain'-txt Checkstyle report, which can be part of the reports of the broken build. This feels very clumsy (and Checkstyle should be considered just a placeholder for other reporting tools, like FindBugs or JUnit). So of course I wouldn't need the whole site to be created, but just the (HTML)-report of the tool that failed the build. This right now I'm not able to solve. How do you inform your developers about CheckStyle or FindBugs errors / broken build in a convenient way as part of your CI ? Cheers Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
