Continuous Deployment

December 16, 2006 on 7:55 am | In Continuous Integration |

As a developer I want a continuous deployment server that grabs every successful build from my continuous integration server, deploys it and tests that its been deployed correctly. Then when it comes to the end of an iteration, I can use the last successful deployment and just switch it over to live.

Deploy Successful

2 Comments »

RSS feed for comments on this post. TrackBack URI

  1. I re-read this and realized that I missed a trick, surely a Continuous Deployment server should continually take the last successful build and deploy it to a ready-to-go live system. It should then be possible to switch from old to new with no downtime.  Build, deploy and release at the flick of a switch.

    Comment by chris.probably — December 16, 2006 #

  2. […] A lot of people do Continuous Integration these days (even if that just means source control and CruiseControl). But very few teams seem to do any form of Continuous Deployment. The point of Continuous Integration is to detect integration problems as quickly as possible and to reduce the risks involved in a deferred integration. A deferred integration is something that will delay the release and may take an unknown amount of time and involve an unknown amount of problems. As Martin Fowler says in his article: “you are putting yourself into a complete blind spot right at one of tensest parts of a project” […]

    Pingback by chris clarke » Continuous Deployment As A Practice — May 26, 2007 #

Leave a comment

XHTML: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>

Powered by Cheese.     RSS Entries Feed.     RSS Comments Feed     ^Top^