PDA

View Full Version : Subversion update command issues


patsissons
06-30-2008, 05:07 PM
I created a subversion update step today and found that it didn't actually do what I expected it to do. Maybe I am missing something, so I figured I would post my situation.

I created the subversion update step and filled in all the details (basically, I copied a subversion checkout step that I had created previously and changed 'checkout' to 'update'). The problem now is that the generated command that gets executed tries to update the subversion server URI rather than the working directory URI that I would have expected.

I am guessing that this does work if you use the 'file' protocol and then fill in the details properly. I would much rather the update command use the working directory field instead for consistency's sake (or at least allow that to be set as an option). This is mostly because the file protocol will not allow me to pass in a windows explorer URI (which i already use for the working directory in my checkout step).

kinook
07-01-2008, 11:17 AM
The fields on the Repository tab and the 'Working directory for local files' field on the Subcommand tab have different purposes. The former specifies the location of the Subversion repository, while the latter specifies the local path to retrieve files to.

http://svnbook.red-bean.com/en/1.4/svn.serverconfig.html

Boris
03-21-2014, 02:53 AM
I created a subversion checkout step and the program worked correctly. Then I changed checkout to update and received the following message: 'http://wiki.a0d/svn/TortoiseSVN/trunk' is not a local path. Tell me, please, how can solve this problem

kinook
03-21-2014, 07:38 AM
The svn update command requires a local path (or no path at all), not a URL.
http://svnbook.red-bean.com/en/1.7/svn.ref.svn.c.update.html

GrahamS
08-13-2014, 05:19 PM
I got a similar error message to "'http://wiki.a0d/svn/TortoiseSVN/trunk' is not a local path". If you have a SVN set up with 'trunk', 'tags' and 'branches' subdirectories and check out from the trunk directory (rather than the repository root) then the VBP svn update command will give the above error. The command line "svn update /path/to/working/directory" will update the working copy as desired. It would appear to me that the VBP svn update command is not translating to the simple command line that you would expect.

If you check out from the repository root then the VBP svn update command works as expected.

I've resorted to using the "run program" action with a %DOSCMD% to run the "svn update /path/to/working/directory" directly