3 ms·

Could someone name other companies that do continuous deployment? I've only heard that IMVU uses buildbot.

brainsik 16y ago
Buildbot is used for continuous integration, which is a big step along the path to continuous deployment. A lot of companies are doing this today. Fewer are doing continuous deployment. kaChing has some posts about their setup: http://eng.kaching.com/2010/05/deployment-infrastructure-for.html http://eng.kaching.com/2010/05/deployment-infrastructure-for... http://eng.kaching.com/2010/06/applied-lean-startup-ideas-continuous.html 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 http://www.justin.tv/startuplessonslearned/videos There's a lot of momentum towards this. The company I'm at is working to get there.
- Lewisham 16y ago
  Yeah, it's important to make the distinction between continuous deployment and continuous integration. 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.
sv123 16y ago
I believe facebook does it as well, trying to find a video I saw from a while back to post.
cwinters 16y ago
Etsy (not surprising since John Allspaw from flickr is head of ops): http://www.southsearepublic.org/article/2340/read/etsys_continuous_deployment_process/deploying_code_to_production_safely_and_quickly/ http://www.southsearepublic.org/article/2340/read/etsys_cont...
MartinCron 16y ago
Automattic/Wordpress.com does either automated Continuous Deployment or have their deployments so streamlined that releases are made very frequently and are (almost always) non-events.
eries 16y ago
IMVU has done continuous deployment for many years (way before it was cool). For details, I think this presentation is probably the best: http://www.slideshare.net/bgdurrett/sds-2010-continuous-deployment-at-imvu http://www.slideshare.net/bgdurrett/sds-2010-continuous-depl... I've also contributed a chapter on it to the new O'Reilly Web Operations book: http://bit.ly/WebOperations http://bit.ly/WebOperations
- shykes 16y ago
  As far as I'm concerned, IMVU made continuous deployment cool.

Buildbot is used for continuous integration, which is a big step along the path to continuous deployment. A lot of companies are doing this today. Fewer are doing continuous deployment. kaChing has some posts about their setup: http://eng.kaching.com/2010/05/deployment-infrastructure-for.html http://eng.kaching.com/2010/05/deployment-infrastructure-for... http://eng.kaching.com/2010/06/applied-lean-startup-ideas-continuous.html 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 http://www.justin.tv/startuplessonslearned/videos There's a lot of momentum towards this. The company I'm at is working to get there.

Lewisham 16y ago
Yeah, it's important to make the distinction between continuous deployment and continuous integration. 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.

sv123 16y ago

I believe facebook does it as well, trying to find a video I saw from a while back to post.

cwinters 16y ago

Etsy (not surprising since John Allspaw from flickr is head of ops): http://www.southsearepublic.org/article/2340/read/etsys_continuous_deployment_process/deploying_code_to_production_safely_and_quickly/ http://www.southsearepublic.org/article/2340/read/etsys_cont...

MartinCron 16y ago

Automattic/Wordpress.com does either automated Continuous Deployment or have their deployments so streamlined that releases are made very frequently and are (almost always) non-events.

eries 16y ago

IMVU has done continuous deployment for many years (way before it was cool). For details, I think this presentation is probably the best: http://www.slideshare.net/bgdurrett/sds-2010-continuous-deployment-at-imvu http://www.slideshare.net/bgdurrett/sds-2010-continuous-depl... I've also contributed a chapter on it to the new O'Reilly Web Operations book: http://bit.ly/WebOperations http://bit.ly/WebOperations

shykes 16y ago
As far as I'm concerned, IMVU made continuous deployment cool.