For quite a while, I was using Hudson on a small EC2 instance which worked pretty well and does have the benefit of being cheap and pretty hands-off once you set it up. I have pretty detailed walkthrough and setup instructions here and it works with cuke, capybara and github:
http://blog.wakatara.com/2010/12/12/installing-a-hudson-ci-server-on-amazon-ec2-with-cucumber-and-capybara-and-github-integration/ Someone commented recently they worked fine with Jenkins, so if you wanted to go that route, you should be good to go. YMMV. (I should really update that post and the whole thing to Jenkins actually... hmmm...) ciao ! Daryl. On Fri, Jan 27, 2012 at 7:24 AM, Dmytrii Nagirniak <[email protected]> wrote: > Hi guys, > > Just wondering what CI servers you are using and which ones you personally > like (or don't). > > What I need from it is pretty common stuff, but just couple of things: > > > - run specs, cucumber features, JavaScript unit tests > - deploy to staging and production (manually and automatically) > - nice UI and easy to read failure reports > > > I have been using TeamCity which has worked pretty well. > > Also do you care (or should one care?) about isolating the gems she > between the builds (maybe with RVM gem sets or similar)? > > Cheers, > Dmytrii > > -- > 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.
