Nikita Skvortsov

Hello, Would you mind attaching a build log and teamcity-agent.log files (latter can be found in TeamCity agent machine)? 9 июня 2016 г. 23:57 пользователь "nadilas" [email protected] написал: > Hey...

Please, check that user "teamcity" has proper permissions on _target_ machine 25 июня 2016 г. 14:11 пользователь "rtchavali" [email protected] написал: > while using ssh exec sudo command it is failing...

Would you mind giving more details? What were the settings? What did you expect to happen? What happened?

Hello, Thank you for the description. Unfortunately, symlinks preservation is not yet implemented. Should be doable using smbj library.

thanks for sharing the workaround!

Thank you for the request. As a workaround, did you try using `SSH Agent` build feature? https://www.jetbrains.com/help/teamcity/ssh-agent.html

1. Select "verbose" messages level on build log tab to see exact SSH messages exchange. This will tell, why auth fails. 2. Check, that `password` auth type is allowed by...

@aswamca * go to build results, * open build "Build Log" tab * select "Verbose" in "View" combobox * find the SSH debug messages in build log (should have appeared)...

The verbose log that you sent does not contain SSH debug messages It means, you are using old version of plugin or TeamCity server. Please install a latest version of...

Most probably, this is caused by name collision. Client tries to upload _file_ "folder1\folder2\my.folder.name", but a _directory_ with same name exists on remote server. If you face this issue once...