A previous project I worked on used Jenkins with a vagrant plugin to run concurrent tests in isolated VMs.
It took a bit of setting up, but once it got going it was amazing and dropped our build time from >20 minutes to <5 minutes. The downside was that it became tricker to understand the "state of the build" at a glance. Instead of checking 1 project, you had to check 6 (unit tests, acceptance tests 1, acceptance tests 2, etc). We also tried parallel_tests for a while and it mostly worked, but we ran into a few issues with parallel acceptance specs stepping on each others toes. James On 22 November 2012 13:12, Sebastian Porto <[email protected]> wrote: > Hi Guys > > There was a discussion the other day about CI server and it was mention > several times how good it is to run the tests in parallel. I am intrigued > by this and will like to implement this. But I don't know where to start. > > What is your approach for running CI test in parallel? We are using > TeamCity at the moment, were using Jenkins before. And Rspec. > > Thanks > Sebastian > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/rails-oceania/-/HqhReVKyNx0J. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
