First article I read on Continuous Deploymemt was http://timothyfitz.wordpress.com/2009/02/08/continuous-deployment/

There was a followup post as well - http://timothyfitz.wordpress.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/

IMVU is a fairly large website that hosts a 3D 'world' similar to Second Life.

Another post with some interesting ideas - they have a script that blocks commits if the 'build' is broken http://radar.oreilly.com/2009/03/continuous-deployment-5-eas.html

Good article talking about the personality and team aspects of CD: http://www.startuplessonslearned.com/2009/06/why-continuous-deployment.html

A Summary of some recent articles at InfoQ: http://www.infoq.com/news/2009/03/Continuous-Deployment

-----

Discussion -

Rails seems to be a good environment for this

challenges - creating deployable binary artifacts

doing it from the start

Where do regression tests come in? Automated tests?

Book coming out - check the rough cut - http://continuousdelivery.com/