Ibuildings - Blog - ibuildings.nl

Blog

Ibuildings, blog

Blog

Guido's blog

Guido van Biemen Guido van Biemen
Technical Support Engineer
 Zend PHP5 Certified Engineer
Guido is one of the developers at the Ibuildings Support Team, dealing with change management and maintenance of our installed base of software. He is a major contributor to the Achievo project management application and an avid online gamer.

Donderdag, 31 juli 2008

Client side migration from CVS to SVN

Migration from CVS to SVN is often described on the repository server side only. When migrating you would normally delete your CVS working copies and check out a fresh one from SVN. However in case of a live website you may not want to reinstall the entire working copy (including locally changed configuration files and unversioned files). Reinstalling the website may cost time, increase server load and cause website downtime.

To overcome this problem you can convert the working copy from a CVS working copy to an SVN working copy, by replacing the CVS meta data with SVN meta data directories in your working copy:

  1. First make sure your CVS version is up to date and SVN contains a 100% equal version of your code (this is very important!). You may accomplish this by exporting your CVS repository and importing it into an SVN branch.
  2. Checkout a fresh working copy out of SVN and delete all files from it, leaving only its directory structure and SVN meta data (.svn folders) intact.
  3. Copy the working copy you just created over your environment you want to switch.
  4. Remove all CVS meta data (CVS folders) from your environment.
  5. After the transition you can verify whether the migration was successful by issuing "svn status"


On Linux or other UNIX based systems you may accomplish this using the following commands (assuming your www folder contains the environment you want to switch):

CODE:
# Check out a temporary svn working copy
svn checkout http://svn.example.com/myrepo/trunk temp

# Delete all content except the directory structure and .svn folders
cd temp
find -type f|grep -v \.svn|xargs rm
cd ..

# Copy the .svn meta data to your www folder
cp -r temp/* www/
cp -r temp/.svn www/

# Remove the temporary svn working copy
rm -rf temp

# Remove all CVS meta data from the environment
cd www
find -name CVS|xargs rm -r
cd ..


After doing this you can verify the version control status of your working copy by issuing "svn status". Of course you should test this on your testing environment first to make sure this migration doesn't pose any unforeseen problems before you apply this on your live website.
Geplaatst door Guido van Biemen op 07:17 | Reactie (1) | Trackbacks (0)
Tags voor deze bijdrage: , ,
Share

Trackbacks
Trackback-URI voor dit artikel

Geen Trackbacks

Reacties
Geeft reacties weer als (Lineair | Samengevoegd)

Very inventive indeed, overlaying a CVS working copy with new SVN meta-data. Although this "hack" really does not promote adhering to best practices on version control. Migrating from CVS to SVN is the perfect time to get rid of all those ugly local changes!
#1 Bill Stegers (Homepage) op 31-07-2008 13:13 (Beantwoorden)

Reactie toevoegen

BBCode opmaak toegestaan
Met sterretjes wordt tekst *vet* gemaakt. Met underscores kan een _woord_ onderstreept worden.
Standaard emoticons zoals :-) en ;-) worden geconverteerd naar plaatjes.
Email adressen worden niet getoond en zijn alleen zichtbaar voor de blogger.

Om het posten door robots tegen te gaan, gelieve de letters die je in het plaatje ziet over te typen. Je commentaar wordt enkel gepost wanneer de letters overeen komen. Je browser dient cookies te ondersteunen (standaard staat dit aan), of je commentaar kan niet geverifieerd worden.
CAPTCHA
 
 

Benelux (wijzig / change)