>hi there. > >just wondering what the group uses in their workplaces to do source control. >we use source safe, and i know there is subversion and the other tools >out there, but really my question is... how do you handle taking your cf code >or other code, and publish that to a staging environment, and then take that >and put it out in the production environment? > >are there tools that can take the codebase and distribute it out? or >am i dreaming? > >thanks >tony
We use CVS and shell scripting for our CF code. Once something is committed to the respository and tagged, we run a shell script to deploy it to the QA server. At home I use SVN and the subversion plugin in Eclipse to handle the source control. I've written an ant script to do the deployment to my server on save. Our java developers use Cruise Control for continuous integration. It monitors the CVS repository, and if there's a change it checks out the project, runs Maven2 to compile the jar files and test them. If all the tests are passed Cruise Control then deploys the jars to the QA server for integration testing. If everything passes QA we deploy to the production servers using another shell script. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Enterprise web applications, build robust, secure scalable apps today - Try it now ColdFusion Today ColdFusion 8 beta - Build next generation apps Archive: http://www.houseoffusion.com/groups/CF-Community/message.cfm/messageid:246158 Subscription: http://www.houseoffusion.com/groups/CF-Community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5
