We manage a range of client sites built in Wordpress and Joomla and these require regular updates to the core CMS and extensions. We keep these sites in subversion and place updates in subversion. We try to use a single revision for this.We face some difficulties in making this process efficient, over time we would like to automate it, so we can offer the process on a fixed price basisThe process is currently as followsmake copy of whole foldersvn status |grep '^!' |sed 's/^!\s*/svn delete /g' |sed 's/$//g' |shsvn updatesvn status |grep '^?' |sed 's/^?\s*/svn add /g' |sed 's/$//g' |shsvn ci -m Commit messagesvn remove -mtemporarily remove http://subversion.repository.com/svn/automatem/projects/client/trunk/project/foldernameSteps 5-6 are usually repeated multiple times.What I'm looking for help withwe are using subversion version 1.6 and 1.7, because there are no .svn folders in 1.7 in subdirectories, I wonder if the process is much easier on 1.7?we've added step 3 because it reduces the number of repeats in steps 5-6. However this was just trial and error and I can't quite get my head around why this isAs I understand it, the issue in step 5-6 is that when the an extension is updated, it may delete a whole folder and then re-insert that folder with changed files. In subversion 1.6, this would remove the .svn folder, which causes a 405 Access denied error (the folder gets added, but already exists in svn). What I would need is something that inserts all .svn folders back into my working copy if the folder already exists in svn. Is there a way to accomplish this?Any other improvements of course appreciated.
CMS updates into subversion -> review process
svn;process;review