I have a setup where I am running a WinSCP script from Jenkins deployment server. Basically I point Jenkins to a batch file that runs commands with the /command flag:
call "C:\Program Files (x86)\WinSCP4\WinSCP.exe" /log="C:\Program Files (x86)\WinSCP4\log-%1.txt" /command "option batch abort" "option confirm off" "open scp://firstname.lastname@example.org" "synchronize remote blah blah blah" "close" "exit"
This worked well with WinSCP 4.3.8 but when I updated to 5.1, Jenkins just hangs. I can run the script just fine logged in as the jenkins user on the actual server but cannot run it from the jenkins web interface. The session data is store in an .ini file and I did everything I was supposed to do according to the docs to run scripts. 4.3.8 works after all.
Has anyone else encountered something similar? Perhaps from a Hudson build machine?