You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
This question is in reference to Atlassian Documentation: Using the SCP task in Bamboo
When trying to use the SCP module to deploy files to a remote server, the task fails because the user cannot perform the set mode action. How do I prevent the SCP module from trying this?
Failed to upload <directory>, Remote SCP command had error: scp: <directory>/<subdirectory>/<file>: set mode: Operation not permitted
A possible workaround is to simply use a Script Task and call `scp` yourself, which will by default not attempt to preserve times. I'm not yet seeing any downsides to doing this.
It's not clear to me why SSHJ would implement the opposite behavior as a default. Atlassian, is there no way to override that in the SSHJ API?
Hello @John Donahue,
There is no way to modify behaviour of SCP task in runtime to avoid preserve time action.
SCP plugin uses SSHJ 0.12.0 library for scp operations and it checks if file from file system is being uploaded then it preserve timestamp on destination file. The only way to skip this action is to use not FileSystemFile for upload, but InMemorySourceFile which doesn't have timestamp. We don't have plans to support this functionality in visible future
bamboo-scp-plugin is open source and you can modify it for your needs: https://bitbucket.org/atlassian/bamboo-scp-plugin