Comments on: Weekly Release Blog #23 – Continuous Deployment… to test? http://exortech.com/blog/2009/04/28/release-blog-23-continuous-deployment-to-test/ Peripatetic thinking Sat, 15 Jan 2011 18:20:06 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Michael Ossareh http://exortech.com/blog/2009/04/28/release-blog-23-continuous-deployment-to-test/comment-page-1/#comment-307 Michael Ossareh Sat, 09 May 2009 19:20:45 +0000 http://exortech.com/blog/?p=150#comment-307 Hi - nice post! I saw this and thought of your endeavors: http://www.zeroturnaround.com/javarebel Hi – nice post! I saw this and thought of your endeavors: http://www.zeroturnaround.com/javarebel

]]> By: Nivi http://exortech.com/blog/2009/04/28/release-blog-23-continuous-deployment-to-test/comment-page-1/#comment-306 Nivi Sat, 09 May 2009 17:45:03 +0000 http://exortech.com/blog/?p=150#comment-306 I think that starting with crappy continuous deployment lets you understand what you need to do great continuous deployment. Instead of anticipating needs, you discover them in the regular course of business and then build solutions for them. This lets you take advantage of the 80/20 rule. You naturally discover the issues that are causing 80% of the problems and you fix them with 20% of the effort. It is another instance of You-Ain't-Gonna-Need-It in action. It's like when you start with a code base that doesn't have test coverage. You don't go and write a billion tests. Instead, bugs come up in regular use, then you write tests for the bugs and, in the process, get good test coverage via the 80/20 rule. You wrote, "Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible." I think you were applying batch-thinking to the process of building your software development process. Instead, going immediately to continuous deployment is an example of one-piece flow in the factory where you're building your process. That's very cool. I think that starting with crappy continuous deployment lets you understand what you need to do great continuous deployment. Instead of anticipating needs, you discover them in the regular course of business and then build solutions for them.

This lets you take advantage of the 80/20 rule. You naturally discover the issues that are causing 80% of the problems and you fix them with 20% of the effort. It is another instance of You-Ain’t-Gonna-Need-It in action.

It’s like when you start with a code base that doesn’t have test coverage. You don’t go and write a billion tests. Instead, bugs come up in regular use, then you write tests for the bugs and, in the process, get good test coverage via the 80/20 rule.

You wrote, “Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.”

I think you were applying batch-thinking to the process of building your software development process. Instead, going immediately to continuous deployment is an example of one-piece flow in the factory where you’re building your process. That’s very cool.

]]>