-
Bug
-
Resolution: Unresolved
-
Major
I am trying to copy contents inside of a folder(whcih is Jenkins workspace) to another reomte location using sshPut. put always copying full folder instead of contents.
In below example it always trying to copy test folder to destination location.
if the same command executes for the second time it giving below error.
Failed SFTP MKDIR: <host address>:$SERVER_PATH/test
example code:
sshPut remote: remote, from: "$BUILD_NUMBER/test/",into: "$SERVER_PATH"
Installed SSH Pipeline Steps version is 2.0.0
[JENKINS-58778] [ sshPut ] unable to copy only contents inside folder. put always copying full folder
Kiran Kumar Gangadi
created issue -
Kiran Kumar Gangadi
made changes -
| Description |
Original:
I am trying to copy contents inside of a folder(whcih is Jenkins workspace) to another reomte location using sshPut. put always copying full folder instead of contents. In below example it always trying to copy test folder to destination location. if the same command executes for the second time it giving below error. Failed SFTP MKDIR: <host address>:$SERVER_PATH/test example code: *sshPut remote: remote, from: "$BUILD_NUMBER/test/",into: "$SERVER_PATH"* |
New:
I am trying to copy contents inside of a folder(whcih is Jenkins workspace) to another reomte location using sshPut. put always copying full folder instead of contents. In below example it always trying to copy test folder to destination location. if the same command executes for the second time it giving below error. Failed SFTP MKDIR: <host address>:$SERVER_PATH/test example code: *sshPut remote: remote, from: "$BUILD_NUMBER/test/",into: "$SERVER_PATH"* Installed [SSH Pipeline Steps|https://wiki.jenkins.io/display/JENKINS/SSH+Steps+Plugin] version is [2.0.0|https://jenkins-test.basf.net/apdl/pluginManager/plugin/ssh-steps/thirdPartyLicenses] |
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Okay override option is only available for sshGet but for the put you would need to delete the folder before we create it again. or Use sshRemove step
Hokwang Lee
added a comment -
Hello.
Can you let me know more detail example for filterBy and filterRegex?
I want to scp some/folder/*.tar.gz to remote server's /output/ path.
In this case, how can I do that?
I can't find solution in docs and googling and so many test in my PC.
Many thanks,
Hokwang Lee
added a comment - nrayapati
Hello.
Can you let me know more detail example for filterBy and filterRegex?
I want to scp some/folder/*.tar.gz to remote server's /output/ path.
In this case, how can I do that?
I can't find solution in docs and googling and so many test in my PC.
Many thanks, 
Christian Ciach
added a comment - I second this request and I couldn't find a solution for this, too.
Christian Ciach
added a comment - I second this request and I couldn't find a solution for this, too. Maybe we could do something like that as a workaround:
findFiles(glob: 'Build/rpms/*.rpm').each { rpmFile -> sshPut remote: remote, from: rpmFile.path, into: '/data/mirror/rpm-repo' }
This feels a bit dirty this probably has negative performance implications, because this establishes a new SSH-connection for each file.
It would be great if this plugin could provide a "flatten" parameter for the sshPut-step, like the publish-over-ssh plugin: https://wiki.jenkins.io/display/JENKINS/Publish+Over#PublishOver-Flattenfiles
Or, alternatively, allow a wildcard for the "from"-parameter of the sshPut-step, so we could use "Build/rpms/*" instead of "Build/rpms" as the source.
The underlying library allows many kinds of "from" parameters (like Iterables), not just Strings. Maybe this jenkins plugin could be modified so that not only Strings are permitted as the "from" parameter? At least maybe allow Iterables, too?
Christian Ciach
added a comment - - edited Maybe we could do something like that as a workaround:
findFiles(glob: 'Build/rpms/*.rpm' ).each { rpmFile ->
sshPut remote: remote, from: rpmFile.path, into: '/data/mirror/rpm-repo'
}
This feels a bit dirty this probably has negative performance implications, because this establishes a new SSH-connection for each file.
It would be great if this plugin could provide a "flatten" parameter for the sshPut-step, like the publish-over-ssh plugin: https://wiki.jenkins.io/display/JENKINS/Publish+Over#PublishOver-Flattenfiles
Or, alternatively, allow a wildcard for the "from"-parameter of the sshPut-step, so we could use "Build/rpms/*" instead of "Build/rpms" as the source.
The underlying library allows many kinds of "from" parameters (like Iterables), not just Strings. Maybe this jenkins plugin could be modified so that not only Strings are permitted as the "from" parameter? At least maybe allow Iterables, too? 
Piotr S
added a comment - Im facing this problem now. This is a valid issue.
Exactly like described the workspace folder is forced and its creating very inconsistent behavior.
sshPut remote: remote, from: "${env.WORKSPACE}/"+"/", into: "/srv/backuproot"+"/"
above code would sometimes create:
/srv/backuproot/backupMake_dev2/<files here>
but if previus pipeline didnt finish (valid case from me) jenkins will create 'backupMake_dev2@tmp' and on target sometimes i end up with:
/srv/backuproot/backupMake_dev2@tmp/<files here>
Expected behavior:
/srv/backuproot/<files here>
Is it possible to do achieve the expected behavior in any way?
--------------------------------------------------------------------------------------
With filter its also not helping:
sshPut remote: remote, from: "${env.WORKSPACE}/"+"/", into: backuproot+"/", filterBy: "name", filterRegex : /\.json$/
above code creates workspace folder on target like so:
/srv/makeBackupAuto/backupMake_dev2/config.json
Expected:
/srv/makeBackupAuto/config.json
The only workaround i can think of is to mv the files in another step after "put" but i would like to avoid that.
Piotr S
added a comment - Im facing this problem now. This is a valid issue.
Exactly like described the workspace folder is forced and its creating very inconsistent behavior.
sshPut remote: remote, from: "${env.WORKSPACE}/" + "/" , into: "/srv/backuproot" + "/"
above code would sometimes create:
/srv/backuproot/backupMake_dev2/<files here>
but if previus pipeline didnt finish (valid case from me) jenkins will create 'backupMake_dev2@tmp' and on target sometimes i end up with:
/srv/backuproot/backupMake_dev2@tmp/<files here>
Expected behavior:
/srv/backuproot/<files here>
Is it possible to do achieve the expected behavior in any way?
--------------------------------------------------------------------------------------
With filter its also not helping:
sshPut remote: remote, from: "${env.WORKSPACE}/" + "/" , into: backuproot+ "/" , filterBy: "name" , filterRegex : /\.json$/
above code creates workspace folder on target like so:
/srv/makeBackupAuto/backupMake_dev2/config.json
Expected:
/srv/makeBackupAuto/config.json
The only workaround i can think of is to mv the files in another step after "put" but i would like to avoid that. Piotr S
made changes -
| Labels | Original: plugin | New: plugin ssh-steps-plugin |
Please use filterBy, filterRegex options to copy contents of the folders instead of coping the entire folder, and also use
override: true option to override the contents.