http://www.codewrecks.com/blog/index.php/2009/05/29/going-in-production-as-often-as-you-can/ Wrecks of code floating in the sea of Internet Mon, 06 Sep 2010 12:34:55 +0100 http://wordpress.org/?v=2.9.2 hourly 1 http://www.codewrecks.com/blog/index.php/2009/05/29/going-in-production-as-often-as-you-can/comment-page-1/#comment-2492 alkampfer Sun, 31 May 2009 08:06:26 +0000 http://www.codewrecks.com/blog/index.php/2009/05/29/going-in-production-as-often-as-you-can/#comment-2492 When you have multiple customers I think that it is even more important to have a developement environment with continuos integration. Since you have multiple production machine, located at different places, with different environment, etc etc. If your developers are used to work with continuosly live system, it would be simplier to manage such as scenario. Maybe you can keep in your dev environment a list of virtual machines where you have for each one one of your major release of your software. The like to have scenario is something like this. Suppose your software had 3 major version in production: 2.2, 2.4 and 2.6; you create three virtual machines with these version, and at each checkin or once a day, you run all the update scripts to take these versions to the actual one, then run some tests to verify that everything is ok. After each set of test you simply restore a snapshot backup of the virtual machines, so they are clean again for the next test. Alk. When you have multiple customers I think that it is even more important to have a developement environment with continuos integration. Since you have multiple production machine, located at different places, with different environment, etc etc. If your developers are used to work with continuosly live system, it would be simplier to manage such as scenario. Maybe you can keep in your dev environment a list of virtual machines where you have for each one one of your major release of your software.
The like to have scenario is something like this.
Suppose your software had 3 major version in production: 2.2, 2.4 and 2.6; you create three virtual machines with these version, and at each checkin or once a day, you run all the update scripts to take these versions to the actual one, then run some tests to verify that everything is ok.
After each set of test you simply restore a snapshot backup of the virtual machines, so they are clean again for the next test.
Alk.

]]> http://www.codewrecks.com/blog/index.php/2009/05/29/going-in-production-as-often-as-you-can/comment-page-1/#comment-2491 Alex Simkin Sat, 30 May 2009 17:56:23 +0000 http://www.codewrecks.com/blog/index.php/2009/05/29/going-in-production-as-often-as-you-can/#comment-2491 You should really define context making statements like this. We have hundreds of clents, some of which do not have IT departmets, so they need to schedule downtime, pay for us to come and install the software, or better yet have parallel 'preproduction environment' that they cannot afford. Not everybody is working for a single client here... You should really define context making statements like this. We have hundreds of clents, some of which do not have IT departmets, so they need to schedule downtime, pay for us to come and install the software, or better yet have parallel ‘preproduction environment’ that they cannot afford. Not everybody is working for a single client here…

]]>