But so far this process just seems to hang doing nothing … is there anything we need to add for Powershell & svn with Octopus deploy … other powershell commands (recycle IIS etc work fine)
Thanks for reaching out. Usually the main reason why Powershell commands hang in Octopus is because the console is waiting for an input that never arrives (because the Tentacle service runs powershell in non-interactive mode). So at the eyes of the user, Octopus just hanged, but it is actually Powershell that’s waiting for something else to happen before continuing.
(from here onwards, keep in mind that i’ve never used SVN and i’m just ranting about my experience with Octopus + Powershell)
On these cases, the usual suspect is “Authentication”. Sometimes you run a command from your server without passing down credentials and it just works because its picking up the credentials from someplace else (powershell session, ws credentials, etc). This of course doesn’t happen when you run the same command from a non-interactive session triggered by a service, so Powershell stays still waiting for you to enter your credentials. A few things to try here:
Does SVN cmd line utility have some sort of parameter where you can pass down your credentials? I’d try that first
Are you running the Tentacle service with an account that has enough permissions on SVN to perform those actions?
Additionally, could you send us the raw log file so we can see how the “hanging” looks like?