On 6/21/07, Cutter (CFRelated) <[EMAIL PROTECTED]> wrote: > OK, quick OT. Moving to using Subversion in our dev environment (yeah!), > but hitting a few stumbling blocks. > > I can 'export' a clean version of my 'HEAD', or any revision. But, I > have a massive (3,000+ template) code base. Not every 'commit' to the > system is tagged, or part of a branch.
I reread your post and noticed this -- not sure what you mean about not every commit is tagged... tags are generally used to bundle up a bunch of changes to move it to qa/integration/uat/whatever. it's a snapshot of the repository status at a particular time you've pasted a label onto. So as you're working in trunk, you decide "this is it", use svn copy to tag it as REL-1.0 and now you've got a reliable point to pull the release from, even while development is continuing in trunk. And as far as branches -- there shouldn't be all that many branches. Folks using SVN typically use branches for feature changes, releases, or in some cases individual developers. The most basic scenario is that everyone's working in trunk, you get to a point where it's ready to move to QA or production or whatever, you tag it, and then you use that tag for deploying. 3000 templates at @ 10kb each (generously large for CF imho) is still not all that much to deploy... 30mb uploads are quite feasible across a DSL modem let alone T1. I routinely deploy an 8gb application (mostly media content) using export from svn across a T1 line (unless it's an emergency - - then we push just the cf templates (assuming a cf prob) or run a USB drive the 30m out to the colo). How (or is it even possible) do I > pull ONLY the modified files from the repository? I have SvnAnt > installed within Eclipse, to utilize Ant with Subversion for creating > builds and deployments, but I'm still struggling to get my head around > all of this. You *could* create a patchfile, which contains all of the differences between two versions of "something" in the repository (eg a file, directory, or entire tree) and then apply the patchfile directly to your previous application to update it -- but that's a pretty unusual approach to build management that will probably bite you in the end. My general experience is that exports are the best way to go, though in some cases using svn checkouts on the *integration* server to manage the initial "build" works fine. Even in that case, the QA/UAT and definitely production builds are typically full exports. > -- > Steve "Cutter" Blades > Adobe Certified Professional > Advanced Macromedia ColdFusion MX 7 Developer > _____________________________ > http://blog.cutterscrossing.com > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:281898 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
