Hi Stefan,
another idea could be to call Maven with the --fail-at-end (-fae)
option. But this doesn't seem to work with Maven 3 anymore. Maybe it
could be worth it for You filing a regression report for Maven 3 at [1].
> #3 ... sound interesting! The most complicated thing here is to share
> data between two builds. But this might be possible with TeamCity
> artifact dependencies.
I think this should work fine. I did something similar for a customer
with TeamCity: A main build created the deployable archives using Maven
and another build was tiggered when the main build finished
(successfully) and used Ant to deploy the archives. I remember that I
configured die 'Artifact Paths' in 'General Settings' to (sort of)
published the relevant files, so that they can be accessed by the
subsequent build (using the 'artifact dependencies' configuration?)
> Also developers would be informed that a build is broken,
> but need to wait until the 'report' build gets scheduled.
I'd say they wouldn't need to wait much more time than they had/have to
when using Your Ant builds. The 'report' build would be triggered
immediately after the other one has finished (using the 'Finish Build
trigger').
[1] http://jira.codehaus.org/browse/MNG
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
