On 09/01/2009, at 2:55 AM, Benjamin Bentmann wrote:
Brett Porter wrote:
Does this mean they all get built in one go, or just a tool to add
them easily?
Yep, the ci-aggregator POM is meant to build them in one go, just
like we do with the Maven plugins over at Apache (cf. [0]). AFAIK,
Maven's build aggregation is the only easy way to get a bunch of
projects building on Hudson without drowning in configurations. Of
course, simply adding a module to this aggregator POM is also an
easy way to add it to the CI run, so I fear I misunderstood the "or"
in your question.
The "or" was really about if it was like Continuum - you add the
aggregator POM, and get configurations for each separately without
having to drown in configurations.
I would be glad to know that all the non-sandbox plugins always
build, but when one fails I'd rather it didn't affect the others.
Fully agreed, but that should be easily dealt with using Maven's -
fae flag, isn't it? In detail, I assume we would be running
something like "mvn -U -B -e -fae clean install" on the ci-
aggregator. Of course, the reactor build itself will still be marked
as failure when a single plugin fails but we should get meaningful
results for the plugins themselves.
That seems the best way to do this. I wouldn't normally expect a
checkin on one plugin to rebuild all of the plugins, but they aren't
my CPU cycles being burnt so it doesn't phase me :)
Go for it - anything you are prepared to do to get it started is an
improvement :)
Cheers,
Brett
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
