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: http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#testFailureIgnore — Yegor Bugayenko, PMP®, SCEA On Thu, Mar 24, 2011 at 10:00 AM, <[email protected]> wrote: > Well, > > I don't consider 'use another tool to overcome your maven problem' as a > valid answer. There are reasons we chose TeamCity over Jenkins. > TeamCity is catching the JUnit failures as well, but I need to care about > any other report as well. > > And right now I'm not able to configure maven in a way that - even when > the build is failing - I get at least a readable HTML report about the > failure (i.e. Checkstyle). > > How do people configure maven, that run tests or findbugs on the console > without a buildserver? Don't they need HTML reports as well? > > Cheers > Stefan > > > > > > > Von: > Stephen Connolly <[email protected]> > An: > Maven Users List <[email protected]> > Kopie: > [email protected] > Datum: > 23.03.2011 23:30 > Betreff: > Re: mvn deploy and site in one go > > > > Jenkins picks up the test failures from the xml reports... maybe you > should switch from TeamCity ;-) > > On 23 March 2011 17:31, <[email protected]> wrote: > Hi Yegor, > thanks for taking the time to share your thoughts. > > >>The only option you have is to run your project twice in your CI > environment > I'm afraid that is no option for us. I planned to use Maven to reduce > build-times (right now dependent projects are checkouted and compiled over > and over again) but running all tests twice would increase build times in > the end. > > >> But think again, are you sure that you want your site to be built if > there are JUnit/Checkstyle failures? > I maybe don't need the full site (which we plan to create only once a week > I guess), when there is a failure. > > But I'm in need of HTML-Reports so that developers can find the cause auf > the failure in those reports quite easily after a build has failed. > TeamCity picks up JUnit-Testfailures automatically from the log - so I > might live with missing HTML-JUnit-reports (as for some reason I have no > luck calling surefire-report plugin after a test-fail). > > But with CheckStyle it's a different story (no explicit support in > TeamCity). Here I need a generic HTML-output which can be uploaded (by > TeamCity) and presented as part of the build. > Right now I can either choose between an HTML output without CSS (looking > ugly) or TXT-output which feels like living in medieval times ;) > I guess if there was a goal that provided the missing CSS-files for the > reports, I'd could make it work like I want. > > Cheers > Stefan > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
