>> Your CI should send developers a link to the build failure. Here is an example reason for failure: >> Foo.java:16: warning: Line is longer than 80 characters. >> How much more convenient can you get?
TeamCity mails look like the following: --------- Build Maven Tests::maven_test_project #11 failed Agent: srvBuildAgt3 Build results: http://buildserver:8080/viewLog.html?buildId=42805&buildTypeId=bt477 -------- this gets you to a web-page with (if I could get it to work) nice formatted HTML reports of all problems (i.e. Findbugs). We even had short messages like 'Findbugs Failed' or 'Checkstyle Failed' in the mail-headers, don't know yet if I'm able to get this tight integration with maven. As this one line: >> Foo.java:16: warning: Line is longer than 80 characters. is a normal console/log output, TeamCity is not able to catch that line up and highlight it :( Is Hudson really getting this single Findbugs-Failure line into it's email-body without any other clutter from the log around it? I definitely don't want full-logs in my mails - sometimes they are >2MB in our (ant) builds. Looking into the logs we had 5 years ago when still running CruiseControl. Now (from our Ant-Builds) we are used to failing builds where devs click on a single link and can instantly go to the FindBugs report which is nicely formatted. This is much faster and convenient than scanning the logs to find the appropiate error-message. We are talking about hundred developers: trained/untrained/rookies/stubborn/students - I want a system easy and intuitive to understand for everyone. -- View this message in context: http://maven.40175.n5.nabble.com/mvn-deploy-and-site-in-one-go-tp4257014p4267319.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
