http://www.build-doctor.com/2009/01/04/sticking-plaster-over-a-gaping-wound/ Helping to deliver working software, one continuous integration build at a time Wed, 21 Jul 2010 04:50:11 +0100 http://wordpress.org/?v=2.8.4 hourly 1 http://www.build-doctor.com/2009/01/04/sticking-plaster-over-a-gaping-wound/comment-page-1/#comment-258 simpsonjulian Mon, 05 Jan 2009 08:09:11 +0000 http://www.build-doctor.com/2009/01/04/sticking-plaster-over-a-gaping-wound#comment-258 That's what I thought, until I got there. Very strong bias towards pointy-click - both in software vendors (hello Bill!) and .NET developers. Dynamic languages very much underused. Also, large number of legacy applications with no easy deploy process. Eeeek! That’s what I thought, until I got there. Very strong bias towards pointy-click – both in software vendors (hello Bill!) and .NET developers. Dynamic languages very much underused. Also, large number of legacy applications with no easy deploy process. Eeeek!

]]> http://www.build-doctor.com/2009/01/04/sticking-plaster-over-a-gaping-wound/comment-page-1/#comment-259 Douglas Squirrel Sun, 04 Jan 2009 20:16:21 +0000 http://www.build-doctor.com/2009/01/04/sticking-plaster-over-a-gaping-wound#comment-259 I'm confused - wouldn't CI properly implemented catch all these problems? You should be deploying to a test environment just as to production, so running all the scripts. No instructions should be needed - all scripted; rollback can be tested too. Maybe there was resistance to testing in this way? I gather the tools were not as good as in the Java world. I’m confused – wouldn’t CI properly implemented catch all these problems? You should be deploying to a test environment just as to production, so running all the scripts. No instructions should be needed – all scripted; rollback can be tested too. Maybe there was resistance to testing in this way? I gather the tools were not as good as in the Java world.

]]>