<< CI Factory - my first day of real use - phew! | Home | CI Factory with NUnit (rather than MbUnit) >>

SubVersion - make sure SVN.EXE and Tortoise are kept in sync when using automated tools

A minor glitch while getting CI Factory up and running. 

I discovered how important it is to make sure that you keep your version of SVN.EXE (command line SubVersion) in step with that of TortoiseSVN. As TortoiseSVN informs you of upgrades, I'd happily updated it to v1.4.x automatically, leaving my SVN.EXE at 1.3.x.

The gotcha was that the installation of CI Factory was fine - it used the older v1.3.x client to create the project tree.  After I had used TortoiseSVN to add some projects, it was only when I forced a rebuild by CruiseControl.NET that I saw errors in the CC.NET interface detailing the SubVersion mismatch.

The issue was that you cannot use older SubVersion clients to update a local tree created by a different SubVersion client.  Quite a reasonable requirement and a terrible 'DOH !' moment on my part.  A quick update of my command line SubVersion tools and all was well in CC.NET.

Print | posted on Tuesday, April 10, 2007 2:29 PM

Feedback

# re: SubVersion - make sure SVN.EXE and Tortoise are kept in sync when using automated tools

left by Mike at 5/6/2008 9:44 PM Gravatar
where do i download svn.exe for windows?

# re: SubVersion - make sure SVN.EXE and Tortoise are kept in sync when using automated tools

left by Liam Westley at 5/7/2008 10:22 PM Gravatar
There is no 'SVN.EXE for Windows' - your best choice is to use TortoiseSVN which hooks directly into Windows Explorer to provide access to SVN repositories.

If you are thinking along the lines of Visual SourceSafe, SourceSafe Explorer I would imagine the closest SVN experience is to use TortoiseSVN and select the 'Repo-browser' option when right clicking on a folder in explorer.

Personally I find the TortoiseSVN direct integration into explorer much more useful than a standalone application. There is nothing like using TortoiseSVN directly within a File Open dialog in an application like Windows Notepad. That means TortoiseSVN 'version control' enables even Windows Notepad.

# re: SubVersion - make sure SVN.EXE and Tortoise are kept in sync when using automated tools

left by ivucica at 5/18/2008 5:46 PM Gravatar
incorrect, svn[.exe] pretty much exists for windows, and it's a command line tool. svnserve[.exe] also exists for windows in the same form. in addition to that, observe, that rapidsvn also exists for windows.

# re: SubVersion - make sure SVN.EXE and Tortoise are kept in sync when using automated tools

left by Liam Westley at 5/18/2008 7:59 PM Gravatar
ivucica,

Quite correct - the command line tool svn.exe does exist for Windows, and there is a svnserve.exe which can be used to have a SubVersion repository running under Windows too. There is a Windows service shell which is very useful for running svnserve.exe without having to logon too. I covered this in a talk at a DeveloperDay 2 in the UK (http://www.developerday.co.uk/, slides and videos, subversion presentation).

I took the view that the comment was really looking for an interactive UI and that definitely is only provided by such items as TortoiseSVN and RapidSVN.

The best integration within Visual Studio is a paid for tool, VisualSVN, but personally I prefer the control of using TortoiseSVN myself rather than have Visual Studio adding files to the repository.

Thank you for the comment, and apologies for my previous glib reply.

# re: SubVersion - make sure SVN.EXE and Tortoise are kept in sync when using automated tools

left by Liam Westley at 5/18/2008 8:04 PM Gravatar
Oops,

And neither of our replies actually stated that SVN.EXE for Windows can be obtained from the main Subversion site; http://subversion.tigris.org/project_packages.html

Select 'Win32 packages built against Apache 2.0' and then download the 'setup.exe', latest version is 'svn-1.4.6-setup.exe'. When you run that setup you will get a '\Program Files\SubVersion' and within that there should be an svn.exe available for command line use.

# re: SubVersion - make sure SVN.EXE and Tortoise are kept in sync when using automated tools

left by Ivan Vucica at 5/19/2008 7:42 AM Gravatar
It's ok; I often make similar mistakes when I'm sleepy :)

By the way, an interesting thing I noticed is that I don't have CLI SVN in my TortoiseSVN installation; I guess they stopped shipping it. Well, I hope they'll add better support for "svn cp" and "svn mv"; it's a real space saver when working with large projects. Think of having same 1MB normal map, but used only temporarily, for fifty files; if it's only a placeholder, it's better to hardlink it using "svn cp" than to physically copy it.

Branch/tag menu option in TortoiseSVN is _using_ the same functionality in the backend - but not _providing_ the same functionality in the frontend ;)

Ah well -- my rant went on too long and a bit offtopic, but at least I mentioned why TSVN is not always good ;)
Title  
Name
Email (never displayed)
Url
Comments   
Please add 1 and 1 and type the answer here:
Copyright © Liam Westley