Starteam migration to Subversion

At work we have been using Borland's Starteam for a while for our SCMS (Source Code Management System).  I don't know it is good or bad, as we have simple team, but when I asked for additionnal licences, I found out that their prices are very high: 1 Named user: 750$, 1 Concurrent user: 3900 (discounted by 50% at the moment I asked for a quote).  And add to that 22% yearly maintenance cost.

As we already started using Subversion for other projects, we decided to move from Starteam to Subversion for all of our projects, but our concern was of course how to import all the project versions from Starteam to Subversion.  Thanks to a nice company named Polarion, it is possible with their svnimporter tool http://www.polarion.com/downloads/svn.php.  This tool is available to migrate from other SCMS to Subversion with support for CVS, PVCS, VSS, ClearCase, MKS and Starteam.

It took me some time to figure out how to run the tool (which is java-based).  At first I just used the tool and dumped data on my own Windows workstation, but when I tried to load the data on my Linux svn server, I got errors.  Also, apparently the Starteam implementation has problem with Starteam tags, but I didn't mind and set it to import the trunk only.  Finally, I managed to run it on my Linux svn server easily and it creates the repo automatically and loads the data in it.  Our biggest project took 88 to import.


Comments

Leo said…
Planning to do that here...
Can you post how did you manage to do? Mini how to?
8:58 AM
ugob said…
Did you download the tool? It is quite self-documented. You have to edit a comfig file and start the command... At first I tried it on my Windows PC, but found out it was easier directly on my Linux-based SVN server.

If you have specific questions, please let me know.
3:06 PM
Post a Comment

Popular posts from this blog

General linux performance troubleshooting

Here's a list of commands that you should execute and then share the output to someone who can help you figure out what resource is the bottleneck in your system. Note, it requires the  sysstat  and  procps  packages (ubuntu and RHEL and its derivatives): uptime vmstat 1 10 iostat -xN 2 10 mpstat -P ALL 3 10 pidstat 1 10 free -mw (or free -m, if your OS doesn't support -w)  uptime is to see the load averages on the system. vmstat is mostly used to tell if the system is swapping or not. If you see significant numbers in the 'si' and 'so' columns, your system is most likely swapping (using the hard drive as RAM), which usually slows performance a lot. iostat is mostly used to determine if your disk subsystem is not able to cope with the load. If you see one or more lines that shows 100 or close almost constantly, it is probably the case.  If it is your swap volume, you probably saw numbers in the 'si' and 'so' columns in the  vmsta
Read more

Asterisk works under OpenVZ (no zaptel)

Hi, Just to let you know that I did a basic test with asterisk on an OpenVZ VE and it works. We only tested SIP connectivity (it would probably be complex to have Zaptel support and I don't really need it). We were able to connect to a VoIP provider using SIP ( unlimitel ) and music on hold works. The only thing I had to change to make it work is to comment out this line in /usr/sbin/safe_asterisk: #TTY=9 # TTY (if you want one) for Asterisk to run on (I guess there is no TTY9 (console # 9) on openVZ since it is a virtual machine and TTY9 is usually a physical console (monitor)). I'll soon put my asterisk server in a VE, I'll let you know how it goes. I also use Unlimitel and ATAs to link my PSTN line and cordless phones.
Read more