How To Migrate From Version Cue to Subversion

If you’ve read anything else on this blog, you’ve probably noticed that there has been an almost unhealthy obsession with Adobe and more specifically their Source Control Server formerly called Version Cue (but dropped as of CS5). I’ve been remiss about adding the last chapter of my Adobe Saga. Since the topic is probably a little stale I’m going to keep it brief and just give a very brief outline of what I did. If anyone has questions about details such as configurations used for Subversion or backup scripts please post a question in the comments and I will fill in the missing pieces. Auto Props settings are at the bottom

  1. Install Visual SVN Server. I used the free version, but we may upgrade at some point. If you’re comfortable setting up SVN on Linux I have no doubt it would work, but VisualSVN was/is so easy I chose that.
    1. We added some settings to the server about checkin/checkout and requires lock but it’s probably not necessary.
  2. Have all users checkin open files/projects into Version Cue.
  3. Check out all projects using Adobe Bridge CS3 (even if you use Version Cue CS4). It’s the only one that checks the files out in a logical file structure.
  4. Use a Subversion Client with appropriate Auto Props settings. We used Cornerstone on the Mac and TortoiseSVN on the PC. Cornerstone was used for adding the files.
    1. By Auto Props I mean they need to be enabled and you need to set all binary (non text) files to “requires lock” in your subversion config file. A sample of our Auto Props settings from the subversion config file are posted at the bottom of the post. The reason for this is that binary files such as images can not be edited simultaneously and therefore should require a lock so no one overwrites another person’s work. Additionally “requires lock” needs to be set before adding the files to subversion or you will have to manually change it for each file afterwards which could take forever.
  5. Create a repository and create users that can access it on the server.
  6. Add the files using Cornerstone. Several projects can be added simultaneously.
  7. Start using SVN instead of Version Cue

That’s it (I hope). Obviously be sure to back up your SVN Server. There are several methods to do so. We use one of the svn hotcopy backup scripts, snapshotting, and we also sync to offsite cloud storage.

If you get stuck, drop me a comment.

Our Auto Props Config:

[auto-props]
### The format of the entries is:
###   file-name-pattern = propname[=value][;propname[=value]…]
### The file-name-pattern can contain wildcards (such as ‘*’ and
### ‘?’).  All entries which match will be applied to the file.
### Note that auto-props functionality must be enabled, which
### is typically done by setting the ‘enable-auto-props’ option.
*.bmp=svn:mime-type=image/bmp;svn:needs-lock=*
*.gif=svn:mime-type=image/gif;svn:needs-lock=*
*.ico=svn:mime-type=image/x-icon;svn:needs-lock=*
*.jpeg=svn:mime-type=image/jpeg;svn:needs-lock=*
*.jpg=svn:mime-type=image/jpeg;svn:needs-lock=*
*.png=svn:mime-type=image/png;svn:needs-lock=*
*.tif=svn:mime-type=image/tiff;svn:needs-lock=*
*.tiff=svn:mime-type=image/tiff;svn:needs-lock=*
*.psd=svn:mime-type=image/psd;svn:needs-lock=*
*.fla=svn:mime-type=application/flash;svn:needs-lock=*
*.doc=svn:mime-type=application/msword;svn:needs-lock=*
*.jar=svn:mime-type=application/octet-stream;svn:needs-lock=*
*.odc=svn:mime-type=application/vnd.oasis.opendocument.chart;svn:needs-lock=*
*.odf=svn:mime-type=application/vnd.oasis.opendocument.formula;svn:needs-lock=*
*.odg=svn:mime-type=application/vnd.oasis.opendocument.graphics;svn:needs-lock=*
*.odi=svn:mime-type=application/vnd.oasis.opendocument.image;svn:needs-lock=*
*.odp=svn:mime-type=application/vnd.oasis.opendocument.presentation;svn:needs-lock=*
*.ods=svn:mime-type=application/vnd.oasis.opendocument.spreadsheet;svn:needs-lock=*
*.odt=svn:mime-type=application/vnd.oasis.opendocument.text;svn:needs-lock=*
*.pdf=svn:mime-type=application/pdf;svn:needs-lock=*
*.ppt=svn:mime-type=application/vnd.ms-powerpoint;svn:needs-lock=*
*.ser=svn:mime-type=application/octet-stream;svn:needs-lock=*
*.swf=svn:mime-type=application/x-shockwave-flash;svn:needs-lock=*
*.vsd=svn:mime-type=application/x-visio;svn:needs-lock=*
*.xls=svn:mime-type=application/vnd.ms-excel;svn:needs-lock=*
*.zip=svn:mime-type=application/zip;svn:needs-lock=*

6 Responses to How To Migrate From Version Cue to Subversion

  1. Ron Frank says:

    Do you have any suggestions for systems to replace Version Cue and Bridge?

    • doug smart says:

      We switched to a combination of Visual SVN server and a couple of different clients. On the Mac we use “Cornerstone” and on the PC we use “Tortoise SVN”. They work pretty well.

  2. Tibor says:

    I am missing the point on how the files and their versions got from version cue repository to the svn repository. Did you move them manually, or there is a helping mechanism that can move projects from version cue to svn?
    Can cornerstone connect somehow to version cue and transfer the files and their versions to the svn repository?
    Thanx in advance for your answer.

    • doug smart says:

      As is necessary to manually copy the files into the new source control system. If I had things to do over again, I probably would have chosen git instead of subversion. Atlassian makes a fantastic source control system called stash that I am looking to convert to in the future. But definitely go with what you know. If you know subversion, it is a great choice.

  3. Tibor says:

    I was hoping for a sollution for moving the files and their versions from version cue to another repository svn or git. I have arround 50 projects with more than 1000 files. Each file has 3 to 10 versions… Moving those one by one could be very time consuming.

    • doug smart says:

      Unfortunately, there’s no real good way to move everything from version cue (including revisions) to another system. You have to copy out the current version of all the files and move those to your new source control. You should be able to check out/update all the files from version cue to your local system and then copy them to the new source control.

Leave a Reply

Your email address will not be published. Required fields are marked *