Re: Getting continuous integration for ActiveMQ *much* faster using CircleCI.

2015-08-10 Thread Kevin Burton
Replying to both of these emails. The issue with maven (like Raul points out) is that there are singletons. IE shared ports, files, etc. With containers, this is removed entirely. Each container has its own set of ports. So going this route (using 24 containers) means a 24 hour build would fini

Re: Getting continuous integration for ActiveMQ *much* faster using CircleCI.

2015-08-10 Thread Raul Kripalani
The Maven Surefire plugin supports running tests in parallel. There's just a few options to activate in the build. However, most of the effort goes into refactoring tests that could yield unexpected results if run in parallel with others in the same host, e.g. discovery tests, port number collisio

Re: Getting continuous integration for ActiveMQ *much* faster using CircleCI.

2015-08-09 Thread Christopher Shannon
I've been thinking about how to improve the speed of builds as well and I think the biggest thing is just getting the tests to run in parallel, regardless of whether or not some form of continuous integration is used. Maven supports parallel tests but it would be more work than just splitting up th

Getting continuous integration for ActiveMQ *much* faster using CircleCI.

2015-08-09 Thread Kevin Burton
Hey guys. Right now the ActiveMQ integration takes a long time. Last time we discussed this (not sure if it was on the list) it was about 24 hours. I’ve been playing with our internal builds and using CircleCI’s parallel integration and I reduced our builds from 50 minutes down to 15. I think 1