http://eng.kaching.com/2010/05/deployment-infrastructure-for...
http://eng.kaching.com/2010/06/applied-lean-startup-ideas-co...
And I believe many of the companies featured in the Startup Lessons Learned conference are doing continuous deployment:
http://www.justin.tv/startuplessonslearned/videos
There's a lot of momentum towards this. The company I'm at is working to get there.
Continuous integration is a fairly simple thing: detect a new source commit, run a battery of tests on it, report back. Hudson is a really good one (of which the original author is a main contributor, and I did some plugin work for a while), and I use it as a fairly fancy looking cron as well.
Continuous deployment, as described in the article, is much more difficult. Not only do you have the slew of tests, but maybe you want more long-running tests that you don't care to run all the time. Maybe you want code reviews. You'll need to automate the actual deployment process and so on.
http://www.southsearepublic.org/article/2340/read/etsys_cont...
I've also contributed a chapter on it to the new O'Reilly Web Operations book: http://bit.ly/WebOperations