I would like to see shorter build cycles. I propose you give it a try in your local workspace and report back the results.
Best, Christian ----------------- Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apache Incubator PMC Member https://www.linkedin.com/pub/christian-mueller/11/551/642 On Fri, Aug 28, 2015 at 12:22 PM, Raul Kripalani <r...@evosent.com> wrote: > Hi team, > > Our tests are taking around 4 - 5 hours to execute on Jenkins CI. > > I think we can reduce this time by making use of the maven-surefire-plugin > parallelisation [1]. Not sure if the partitioning is able to span tests in > multiple projects, though. I've used it in the context of a single Maven > module containing all tests. Does anyone have experience with that? > > Parallelisation opens up the possibility of tests clashing with one another > in terms of port collision, server clustering, etc. More likely to be > noticed on tests that deal with the same technology, e.g. all HTTP tests > starting an HTTP server (even though they are assigned random ports), or > camel-jms and camel-sjms tests starting AMQ brokers, etc. > > I wonder if we could group such tests across test suites and use the > suites* parallelisation modes to avoid the clashing. > > Thoughts? > > [1] > > https://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html > > Regards, > > *Raúl Kripalani* > Apache Camel PMC Member & Committer | Enterprise Architect, Open Source > Integration specialist > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani > http://blog.raulkr.net | twitter: @raulvk >
