Hi Marc, thanks alot for sharing your thoughts. Our buildtimes vary from 30min to 3hour (yeah - big heavy integration tests). This is for 12 products (each having 3-5 build plans for all their maintenance branches) crowding 5 buildagents round the clock.
So this is the reason I definitely don't want to run a testsuite twice but had hoped to optimize the builds with maven: a) if it works => deploy b) if it doesn't => don't deploy, but give me nice reports I can send to devs of all age and experience This is what our Ant scripts do right now (i.e. run some reporting tool, just set a variable when it fails, generate reports, fail the build if variable is set). I'm really curious that - given that Maven exists so long already - it seems such an uncommon use case to get a nice HTML failure report in the case of some build error. So from your proposed solutions: #1 is no option (running tests twice) #2 is no option (don't want artefacts of broken builds deployed) #3 ... sound interesting! The most complicated thing here is to share data between two builds. But this might be possible with TeamCity artifact dependencies. Also developers would be informed that a build is broken, but need to wait until the 'report' build gets scheduled. Doesn't sound like any developer would love me for such a solution :) Well guess right now we are just spoiled by our custom ant-scripts and have to accept 'the maven way', whatever that means (probably reading build logs on a daily basis again) Right now I'm thinking of just bundling the missing css files from the target-folder and manually copying them at the start of the build. Then I could at least use Checkstyle and FindBugs HTML report targets (these only seem to fail after creating the report). And as previously said: for JUnit TeamCity picks ups the XML-Reports anyway so I don't need to cope with surefire-report. -- View this message in context: http://maven.40175.n5.nabble.com/mvn-deploy-and-site-in-one-go-tp4257014p4267328.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
