We use hudson, and we're very happy with it. It can be configured to only email to the person who broke the build.
Aside from that, the annoying part is indeed that the build is broken every hour. On Fri, Sep 4, 2009 at 16:11, Eloy Duran<[email protected]> wrote: > > Hey Ken, > > Sure it's 2 seconds of work to setup a mail filter, but so is signing > up for a specialized mailing list. So that doesn't make it a good > reason. > > I wouldn't be bothered by these CI emails if we'd see one every now > and then. But nowadays, it seems like every other build is broken. > That's the real problem here. > > Are people no longer running the test suite before committing? I can > see how you could get the occasional failure for db drivers other than > the one you use, in fact that's how Rails edge used to be. But it > hasn't been like that for a long time now. > > Ask yourself, for whom is this info interesting? Not for me, I see > those failures when I run the tests of Rails. Especially before I > commit. So I surely hope that it's not being meant as a tool for devs > to no longer run the full suite yourself, because that's not what it's > there for plus it generates noise. If you want that noise, go ahead, I > just kindly ask the maintainers to take it to a specific list, as many > other projects do. > > Cheers, > Eloy > > On Sep 4, 2009, at 3:49 PM, Ken Collins wrote: > >> >> >> I agree with Rob that this list is the right place for it. It's easy >> for individuals to "opt out" by setting up a mail filter. Takes 2 >> seconds. >> >> - Ken >> >> On Sep 4, 2009, at 9:04 AM, Rob Biedenharn wrote: >> >>> >>> >>> On Sep 4, 2009, at 8:57 AM, Nicolás Sanguinetti wrote: >>> >>>> >>>> On Fri, Sep 4, 2009 at 9:47 AM, Eloy Duran<[email protected]> >>>> wrote: >>>>> >>>>> I tend to print them out, beat them with a stick before I set them >>>>> on >>>>> fire, unfortunately gmail was unable to automate this process for >>>>> me. >>>>> >>>>> Seriously though, I think you're right Mike. Actually, I can assure >>>>> you I know of at least a few people who have unsubscribed from the >>>>> list because of this. And as some find them annoying, plus it >>>>> probably >>>>> doesn't do any good, why not just send them to a separate list >>>>> where >>>>> people who actually _do_ want them can get them? >>> >>> Actually, this *is* the right list. The motivation stirred up by the >>> series of CI emails either motivates you to help fix the problem or >>> to >>> unsubscribe. That sounds about right. If seeing the Rails build >>> broken >>> is too much of a burden, then perhaps being on the rails-core list >>> isn't the right place for you. >>> >>> -Rob >>> >>>> >>>> +1 to that >>>> >>>>> Eloy >>>>> >>>>> On Sep 4, 2009, at 2:35 PM, Mike Gunderloy wrote: >>>>> >>>>>> >>>>>> On Sep 4, 2009, at 7:30 AM, Nicolás Sanguinetti wrote: >>>>>> >>>>>>> "Don't forget the build is broken", thus, spam you with emails >>>>>>> until >>>>>>> someone drags his ass over and fixes the build >>>>>> >>>>>> The problem with the "spam emails" approach is that people will >>>>>> treat >>>>>> them as spam. I don't know what the answer is, but I wouldn't be >>>>>> surprised if a lot of the build mails to this group are going >>>>>> right to >>>>>> people's spam folders or being otherwise automatically disposed >>>>>> of. >>>>>> >>>>>> Mike >>>>>>> >>>>> >>>>> >>>>>> >>>>> >>>> >>>>> >>> >>> >>>> >> >> >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
