On 3/10/07, Alexey Verkhovsky <[EMAIL PROTECTED]> wrote: > Email notification from CC.rb works like this: an email is sent every time > the build fails, and once a previously broken build passes. Consecutive > successful builds do not send any notifications. Therefore, in the ideal > world you'd never hear from it.
The 'fixed' builds can omit all the output. I like how Michael's script just gives you the info you need: if the problem is fixed, that's all you need to know. Even for failed builds, perhaps a simple direct URL to the failed build would be most useful. > Once more obscure databases and architectures are added, the amount of > "build failed" notifications may become a problem. Then we can think about > solving it (it shouldn't be too hard to solve). It will be funny, though, if > every commit that breaks the build triggers an avalanche of "HELP!!! BUILD > FAILED!!!" messages from many disconnected CI rigs. :) Have them publish RSS build feeds consumed by planet rails buildfarm which digests and reports here. Clearly, we need more software. Seriously ;-) let's address that when/if it becomes an issue. jeremy --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
