Hello all, When pushing a transfer set up, ssh is not traversing back to the root directory after each file transfer. It just keeps creating directories deeper and deeper until the filesystem can't handle the depth. To the logs:
SSH: Connecting from host [Jenkins] SSH: Connecting with configuration [ftp.arglebargle.com] ... SSH: Creating session: username [skooby], hostname [ftp.arglebargle.com], port [22] SSH: Connecting session ... SSH: Connected SSH: Opening SFTP channel ... SSH: SFTP channel open SSH: Connecting SFTP channel ... SSH: Connected SSH: Remote root is not absolute, getting absolute directory from PWD SSH: cd [release-core/data/core/] SSH: OK SSH: mkdir [api] SSH: OK SSH: cd [api] SSH: OK SSH: put [Application.cfc] SSH: OK At this point, the first file has been transferred to the correct location: release-core/data/core/api/Application.cfc The next file should be put here: release-core/data/core/api/v1/controller.cfc ..but rather than doing a 'cd /' or equivalent, we just keep drilling: SSH: mkdir [release-core] SSH: OK SSH: cd [release-core] SSH: OK SSH: mkdir [data] SSH: OK SSH: cd [data] SSH: OK SSH: mkdir [core] SSH: OK SSH: cd [core] SSH: OK SSH: mkdir [api] SSH: OK SSH: cd [api] SSH: OK SSH: mkdir [v1] SSH: OK SSH: cd [v1] SSH: OK SSH: put [controller.cfc] SSH: OK SSH: mkdir [release-core] SSH: OK My transfer set config: Source files: **/ Remove prefix: Remote directory: /release-core/data/core Versions: Publish over SSH version 1.13 Jenkins ver. 1.609.2 <http://jenkins-ci.org/> Any ideas, fine folks? Thanks! Mike -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8b609ad5-8eb5-4cfd-9026-c62afde2363b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
