On Fri, Sep 4, 2009 at 8:50 AM, Mislav Marohnić<[email protected]> wrote: > On Thu, Sep 3, 2009 at 19:32, Chad Woolley <[email protected]> wrote: >> >> 3. Help fix the build :) > > If there are three commits—A, B and C, where A breaks the build and B,C are > unrelated—I'm wondering why should CI send out emails for errors in B and C > when it detected them in A. > In other words, CI should never re-send the same failures: only if they've > changed. A trivial implementation of this would just be by comparing the > standard output. Thoughts?
"Don't forget the build is broken", thus, spam you with emails until someone drags his ass over and fixes the build. Also, how do you *really* detect it's unrelated? Commit B might use code changed by A, which broke the build, so you don't really know if it doesn't fail. Cheers -foca > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
