Alexey Verkhovsky wrote:
> From my (mixed) experience with running a CI build for Rails [1] for
> the last few months, it only makes sense if the project team cares
> deeply enough about keeping the CI build green. Otherwise, it's
> becomes just an expensive source of permanent annoyance in everyone's
> mailbox.

I agree that this is key to making a CI server work. It seems that so 
far having head be broken for many days is not generally a concern for 
the "most core" of core developers. But it makes it nearly impossible 
for others to get up and running if builds fail and tests don't run 
green. There needs to be a desire from the top to keep the builds working.

However, in order for CI to be useful, it also seems there should be a 
requirement that each behavior-modifying commit must include a test case 
demonstrating the change. If all commits were accompanied by test cases, 
we'd help guarantee behavior failures never happen again while 
simultaneously building out a test kit for other implementations.

The rule on the JRuby project is that commits don't get in without a 
test case, and we're able to stick to that probably 80-90% of the time. 
I think Ruby Core would benefit greatly from a similar policy.

- Charlie