Teamcity will display the failing tests for a build chain in the one place, rather than having you look in build logs in separate places. Which is great, cause our build logs are about 7MB of text.
With regards to parallel acceptance tests, you can either make sure each process has its own instances of DB/search/etc or run those in serial. We've added the ability for only one serial test to be running while running tests in parallel. On 26/11/2012, at 10:20 AM, Ben Hoskings <[email protected]> wrote: > Mm, vagrant is great for this sort of stuff. > > FYI this isn't a problem any more: there's a master build that triggers the 6 > (now 7) parallel builds, and it only passes if all the sub-builds pass. > > The one bit of extra work is that to find each failure, you have to check > multiple build logs, but in practice it hasn't been an issue. > > - Ben > > > > On 26/11/2012, at 9:28 AM, James Healy <[email protected]> wrote: > >> 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. > > -- > 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. > -- 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.
