I've been using Visual Source for 5 or 6 years, and although it has its "quirks", its worked pretty well for me in the past.
At the place I am at now, we use a 5 servers, Dev, SQA, Staging and Production, Control. 1) Dev is where we do our free for all development. 2) SQA is the first line of integration testing, making sure everthing with in the module plays nicely. 3) Staging is where full blown regression testing occurs making sure that the affected modules dont wack other modules. Staging is also replicated from production nightly, which to some degree affects our build timing. 4) Production is of course locked down tighter then fort knox, only three people in the entire company have access, to sys admins and the VP of Tech. 5) Control is where VSS and our bug tracking software live. The reason its seperate is because next to Production this is the most important box you have. If it gets smoked you've lost a lot of very valuable data. Ours is backed up nightly (probasbly should be more often but I have had any success on that arguement yet). With in Source control is 4 projects, dev, sqa, staging and production. All code is shared from dev "upward". When code is to be "released" to SQA the release engineer does a get from the SQA VSS project to the SQA box to mapped drives. Once verified there by QA it is released to Staging via a get from the staging project. Once verified the code is "released" to production via a third get from the production VSS project to the production box. The final step in our release process is to label the production project with verison number and date so that a copy of the site at any give date & time is avaialble. In our cycle code always flows from machine to machine thru a series of gets, shares and rollbacks. HTH, Duane > -----Original Message----- > From: Toby Tremayne [mailto:[EMAIL PROTECTED]] > Sent: Thursday, 27 September 2001 12:53 PM > To: CF-Talk > Subject: OT: Source Controlled Web Development - help needed > > Apologies for the OT post, but I really need some input here... > > We're trying to set up a new dev/staging/production environment with > source > control. One of our major problems / decisions is based aorund the > development cycle and how it works with source control. Obviously the > maxim > "work locally, store globally" is the perfect ideal. When you're > talking > about something like C development this is simple - you just need a > local > compiler. But we're running CF and Spectra, and several of the > developer's > boxes are not capable of running local copies of spectra. > > I don't want a situation where I have to check out a file locally, edit > it > blind, check it back in again, somehow move it to a browseable directory > then refresh the page and see my changes. When I'm trying to debug > something that's going to be a nightmare. Especially if we use CVS > instead > of MS Source Safe (and we'd prefer to implement CVS), because then we > have > an extra client to deal with, thus more alt tabbing all over the place. > > So I'm trying to work out the best solutions - how to handle the serving > of > these pages, where to check out to,(working directories) etc. Can > anyone > lend some insight as to how their company does things, or how best they > might implement something? We can't do away with spectra as we have > several > large jobs requiring it, and we're pretty much stuck with not being able > to > run a local copy of spectra on everyone's box. > > any help at all would be appreciated... > > cheers > Toby > > ------------------------------------------------------------------------ > > Life is poetry, write it in your own words > > ------------------------------------------------------------------------ > > Toby Tremayne > Architect / Developer > Code Poet and Zen Master of the Heavy Sleep > MercuryRed > Lvl 9, 123 Queen st > Melbourne > VIC 3000 > p: +61 3 9605 5035 > m: +61 416 048 090 > ICQ: 13107913 > > ------------------------------------------------------------------------ > ------------------------------------------------------------------------ > DISCLAIMER - All errors and omissions excepted. This message contains > privileged and confidential information intended only for the use of the > addressee named above. If you are not the intended recipient of this > message you are hereby notified that you must not disseminate, copy or > take any action in reliance on it. If you have received this message in > error, please notify Mercury Red immediately > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
