On Fri, Sep 4, 2009 at 11:27 AM, Czarek <[email protected]> wrote:
> Perhaps a timeout within which the build should be fixed? I mean it
> doesn't take hours for CI to detect the problem. And then mail if fix
> doesn't come in time.
That's a good idea. How about this:
1. The first three red builds notify only the core team members (at
the undisclosed location where they congregate)
2. After three red builds (more than enough chances to fix the test,
revert the change, or comment the test), this list starts getting the
failure emails.
Three is arbitrary, it could be more...
> I don't believe committers will want to create and subscribe to a
> separate list. And this is *their* mailing list. Then again, the rest
> of us may want to know if we should "pull" or not.
The core team applied the patch to send notifications to this list,
and can disable them anytime they want.
If the rails core list isn't a place to see and find out about
failures in the rails build, what is? If people are hacking on rails
(which IS the topic of this list), then they probably want to know if
a test failure they see locally is their fault or actually broken in
the official build.
If you don't want to see the notifications, set up a filter, it should
take you less than a minute. The subject lines always have
[CruiseControl] in them. If you can't set up a filter, you are either
lazy or need to learn how to use a real email client. Or just ignore
them (']' in gmail), which takes me about .5 seconds.
-- Chad
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
