In contrast, my requirements for a CI server are: * Trigger "build" via HTTP. * Run one or more unix command(s) * PASS if all commands return a zero exit code. * FAIL on the first command that does not. * Notify some email addresses when interesting things happen.
Jenkins does an exceptionally solid job of this behind it's ugly UI and complicated configuration. As a bonus, our final unix command happens to be "cap deploy", which I highly recommend :) -- Paul On 30/01/2012, at 2:58 PM, Adam Boas wrote: > Currently Simple Cov and Formatted RSpec output. I was also producing Metric > Fu output for Flog, Reek, Flay, Rails Best Practices and Hotspots but > abandoned them due to Rcov dependency issues with Metric Fu. Will look at > getting at least Reek back into the picture next time I have time. > > Adam > > > On 30/01/2012, at 2:49 PM, Ivan Vanderbyl wrote: > >> Hi Adam, >> >> Out of curiosity: What sort of artifacts are you producing? >> >> — Ivan >> >> On 30/01/2012, at 1:40 PM, Adam Boas wrote: >> >>> Actually I think Jenkins kind of sucks. The build pipeline plugin is really >>> the crapiest part of it but it needs a fair bit of work just to get a nice >>> dashboard and display build artifacts nicely (maybe I'm not doing it right >>> but I found the interface really crap). We have been trialing Team City and >>> it is better in some ways and worse in others. On the plus side I don't >>> have to write a bash script to get a ruby build. On the minus side the web >>> based configuration is pretty opaque until you have done it a few times. >>> >>> I am constantly surprised that this is not yet a solved problem. I'll look >>> forward to seeing these hosted options when they are ready. >>> >>> Cheers, >>> >>> Adam >>> >>> >>> On 30/01/2012, at 1:13 PM, Dmytrii Nagirniak wrote: >>> >>>> Thanks to all of you guys. >>>> >>>> So it seems Jenkins is the de-facto here. So be it :) >>>> >>>> I kind of like the hosted option too, but will see how it goes. >>>> >>>> Cheers, >>>> Dmytrii >>>> >>>> >>>> On 29/01/2012, at 7:40 PM, Ben Hoskings wrote: >>>> >>>>> Seconded. Jenkins is the Millennium Falcon of CI: it may not look like >>>>> much, but it's got it where it counts. >>>>> >>>>> Ben >>>>> >>>>> >>>>> Sent from my iPhone >>>>> >>>>> On 29/01/2012, at 11:38 AM, Xavier Shay <[email protected]> wrote: >>>>> >>>>>> Jenkins. >>>>>> >>>>>> UI sucks but the backend is solid, and that's what matter. It has an API >>>>>> if you want it - I haven't, but GitHub built their own CI thing on top >>>>>> of it. >>>>>> >>>>>> Xav >>>>>> >>>>>> On 26/01/12 11:24 PM, Dmytrii Nagirniak 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.
