Sourcesafe to SVN Conversion Questions
Forgive us, but we are a Sourcesafe shop and trying to convert to
Subversion. I'm running into some mismatches with how SS does stuff and
how SVN does it. I'm trying to fit SVN into our process but struggling
with some of the constructs. Any advice you can give would be helpful.
We build some 300+ executables every night and push out this build to
centralize servers so that developers can grab the latest integrated
build and start working.
Today in Sourcesafe, I simply grab the build and set my working
directory and you are set to checkout.
This doesn't really seem to work with SVN/TSVN. The only way I can seem
to get TSVN to recognize a folder is to do a checkout. This will only
work if the directory is empty. So, I would have to check out
everything, and rebuild to start working. The rebuild takes 6 hours, so
this is not possible.
If I do chekouts at the leaf folders, this seems to work, but I need
global properties set from the root for all developers like
bugtraq:message. So, here are the questions:
-Set Working Folder
Is there a way to swap in a delivered build so that TSVN recognizes the
binding to the URL in subversion? Perhaps if I do a checkout on the
build machine and deliver that whole directory? Any other way?
Is there a GetLatest equivalent, or do I have to start with a clean
directory each time? In other words, I can't seem to get files from SVN
unless the target directory is completely empty. I get an error
What is the best way to set global properties like bugtraq:message and
others? When I put them in the config file they do not seem to take
effect. When I put them in the root of a repos branch they do not
propogate to child folders. This may be because I am just getting the
leaf and not all folders in between.
Received on Wed Nov 02 23:27:54 2005
This is an archived mail posted to the TortoiseSVN Users