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).
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).