Andrew, your initial point (that you made redundantly clear by way of caps and repetition) was to never use subversion to move code to production. You then make your detailed case that demonstrates your reasons not to. I agree, in your situation you would not do so. But I fail to see how you can be blind to the fact that not everyone will be in the same, quite horrid by the sound of it (different code per server...), situation. Your arguments for never using SVN in production appear to boil down to:
1. If it is not needed to have the Application run then it should not be there 2. Think of the poor blighters who may inherit your app and are confused by extra data In a situation where using SVN to deploy to production made deployment a great deal easier, faster and more reliable, you could argue that it is helping the application to run (perhaps several hours or days before it would else have been). Future developers will only be confused if the processes aren't documented or they don't read the documentation thats there. I am currently working in an environment where we do merge and merge and merge, etc and we do NOT use SVN to deploy to production; probably rightly so. But I have also been in much simpler environments where using SVN for deployment has made life so much easier and given confidence in the version of the live application. I am 100% confident that using it to go to production in those scenarios is NOT going to turn around and bite me some day. Neither of the above arguments suggest otherwise. I'm sure people interested in this topic would appreciate it if you could add to those points concisely, points that are not case specific. ie. Reasons never to use SVN in production: 1. If it is not needed to have the Application run then it should not be there 2. Think of the poor blighters who may inherit your app and are confused by extra data 3. You will be shot if you do... etc Regards, Dominic 2008/8/16 Andrew Scott <[EMAIL PROTECTED]>: > No I was not concerned about HD space, my view is simple. If it is not > needed to have the Application run then it should not be there, whether > there is plenty of space or not. > > Let me ask you something, if you didn't know about SVN and you picked up a > maintenance job and came across all these extra directories that shouldn't > be there. Are you goiong to know which file is to be used? OR if these extra > dirs and files actually ever get used? > > The point is that you might now what they mean, and why they are there. Bout > put yourself into someone else's shoes and think about the confusion it > would cause. > > Granted having them there is not an issue as such, but why create further > headaches down the track? > > Not everyone has the ability to use a VPN automatically, so automating a > script to export from SVN to production is not always going to be viable > either. For example we have a client where we have to be authorised to > connect to the VPN connection, once we have finished with it is removed. > > The problem with that is that I have to find another solution to do the job, > so the thing is I would prefer to use and build scripts to build the version > into a war file to be deployed, or if in the case of Coldfusion standard, > will build the application to QA as that is internal. Then when it is ticked > off we can then deploy that, but it is still a small extra manual step but > we have no choice when it comes to the VPN connection. > > Eitherway, svn integration will be different to everyone esle. > > But when it comes to deployment from SVN, never use SVN to migrate to > production. When I first mentioned that, people quickly jumped onto the fact > you can export from SVN. Sure, but you are not using SVN to migrate to > production, as you have done an export. I thought that would have been > obvious to most, but it appeared not. > > > -- > Senior Coldfusion Developer > Aegeon Pty. Ltd. > www.aegeon.com.au > Phone: +613 9015 8628 > Mobile: 0404 998 273 > > > > > -----Original Message----- > From: Dana Kowalski [mailto:[EMAIL PROTECTED] > Sent: Friday, 15 August 2008 12:27 AM > To: CF-Talk > Subject: Re: SVN in Production > > This thread is kind of heavy handed. My personal opinion with anything like > this is your mileage will vary. There are simply too many factors to heavy > hand a this is the only way to do it. Everyones configurations, staff, > resources, technical knowledge etc etc vary. You use what works, simple as > that. > > Being over concerned about hard drive space is kind of crazy as well. I'm > not really sure about the shared host portion of the posts as well. If you > are that concerned with security, protocal, space and deployment why would > you EVER be on a shared host.... thats pretty silly. > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;203748912;27390454;j Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:311094 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
