On Fri, Oct 15, 2010 at 6:34 AM, Stephen Connolly <[email protected]> wrote: > I just set up a big fat aggrigator for each of the "test everything > together" projects that I want to run CI over. I use svn:externals to > check everything out and then two maven builders, first to update the > aggregator and all child modules to link them together and the second > to run "verify". That way I never pollute the local repo... and these > types of build run less frequently (hourly), so the slower build is > less of an issue. >
Thanks for this bit, Stephen; I've been considering doing exactly this for a little while, so it's good to know you've already proven it can work well in practice. I think nightly is good enough in my case. I haven't tried using externals with Hudson yet, so I'm curious: does your hourly build always run whether there have been changes or not, or are you getting Hudson to check for updates first? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
