Re: Using maven profiles for easily parallel testing?

2016-11-06 Thread Laird Nelson
On Sun, Nov 6, 2016 at 8:48 AM Kevin Burton wrote: > > If you like to parallize the unit tests themself you have to configure > > maven-surefire-plugin accordingly...I recommend reading the doc about > that > > subject[2]. > > Ah.. interesting. Those changes should be

Re: Using maven profiles for easily parallel testing?

2016-11-06 Thread Kevin Burton
> > > Is this really the time for the tests only or is this the whole build time > including the test time? If it is only the time for running the tests it > means those tests are slow... > > Yeah. I agree. The slow ones are all essentially integration tests. Some take 20-30 seconds as they

Re: Using maven profiles for easily parallel testing?

2016-11-06 Thread Kevin Burton
> > > I'm thinking of a clunky approach of including tests with names starting > with [A-Ma-m] in one build configuration, and those with names starting > with [^A-Ma-m] in another build configuration. These build configuration > could have most of their actual configuration in a build template,

Re: Using maven profiles for easily parallel testing?

2016-11-06 Thread Karl Heinz Marbaise
Hi Kevin, On 05/11/16 22:33, Kevin Burton wrote: We use TeamCity internally (which is great btw) for Maven testing. We have about 2000 tests which we continually integrate on every commit. The problem is that testing takes about 15 minutes from start to end. Is this really the time for the

RE: Using maven profiles for easily parallel testing?

2016-11-05 Thread Sander Verhagen
Thank you! -Original Message- From: burtonator2...@gmail.com [mailto:burtonator2...@gmail.com] On Behalf Of Kevin Burton Sent: Saturday, November 5, 2016 14:34 To: Maven Users List <users@maven.apache.org> Subject: Using maven profiles for easily parallel testing? We use TeamCity internally (wh

Using maven profiles for easily parallel testing?

2016-11-05 Thread Kevin Burton
We use TeamCity internally (which is great btw) for Maven testing. We have about 2000 tests which we continually integrate on every commit. The problem is that testing takes about 15 minutes from start to end. We use -T 16 on our tests and our boxes have 8 cores so this allows some tests to