So I'm a little frustrated. I'm trying to have FinalBuilder create a tag in subversion at the end of a successful build. I have gotten other subversion commands to work commit, Cleanup, Update. But the Copy just won't work, and I've tried every variation of it Source /Destination syntax. Where the command appears to be falling apart is at the file browsing both the source and the destination need to places within the database i.e. (\trunk or \tags\version), but when you browse for the source and destination all you see is the conf, db, hooks, and locks folders.
In regards to the tools being used; all the developers are using TortoiseSVN as their local client, however I had to install VisualSVN on the server just to have a svn.exe for FinalBuilder to spew commands at, and I have the latest version of FinalBuilder.
I had more to this post but it just kept locking up. I kept trying to include the error messages, but after 15 minutes it'd just barf. Maybe it was all the path links.
If the error messages had angle-brackets in them, then the forum software is prone to munching these. Sorry.
There are ways to post such information, but by far the easiest solution is to click “add reply” and then attach a text file to the post, with the error content inside it.
Sorry for the annoyance. If you can post the errors (or, failing that, email them to support at finalbuilder dot com), then it would be a great help.
Looking at the log output, I think it's a bug with the action and the UNC \\server\share syntax.
To confirm this, can you try mapping the share \\Nwksubversion\subversion to a drive letter, and see if it fixes the problem? You can do this with the Map Network Drive action, and optionally use a try/finally block with Unmap Network Drive afterwards.
I tried mapping a drive to \\nwksubversion\subversion, so ended up with X:\SocketProducts\trunk for the source, and I tried \\nwksubversion\subversion\SocketProducts, so that X:\trunk was the source but it just failed. And with letter mapping it seems to think the folder is a work Folder so it searches for \.svn\entries which of course doesn't exist as part of the database.
SVN Work Folder = K:\Builds SVN Command = \\Nwksubversion\VisualSVN Server\bin\svn.exe copy --force-log --non-interactive --revision HEAD X:\trunk X:\tags\test svn: 'X:' is not a working copy svn: Can't open file 'X:\.svn\entries': The system cannot find the path specified. Action Failed \\Nwksubversion\VisualSVN Server\bin\svn.exe returned : 1 Subversion svn Error - Subversion application error : 1 Parms: copy --force-log --non-interactive --revision HEAD X:\trunk X:\tags\test
... got me to a working solution. It seems most of the available documentation about using UNC paths with SVN is out of date (at least for SVN 1.4.) I get the feeling it's really not a recommended configuration, or at the least not a very common one.
The file://[hostname]\[sharename]/[directory]/[directory]/ syntax works. The problem from yesterday was that I needed to added a commit message, because of a forced property on the database. Though wierdly enough when I had tried adding a commit message on some of the previously attempted syntax's final builder would spit back an error message "commit message not needed for this operation".
Well thank you for your assistance. I will say that the Copy method and the help documentation for the command need to be updated, along with the error message that the final builder gives for the command.
The "commit message not needed" message was probably because SVN hadn't found the right database in the first place.
We should have a test build with a working repository builder dialog (for file:// UNC paths) out today. I'll also update the help topic for the Copy action.
The error messages are unfortunately coming directly from svn.exe, so there isn't much we can do about those. I'll see what I can do about tidying up the log output, though.
Please let us know if there's anything else we can help you with.