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.
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.
Benjamin [0] https://grid.sonatype.org/ci/job/plugins-IT-with-maven-2.0.x/ --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
