• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Component/s: copy-to-slave-plugin
• Labels:

  None

[JENKINS-25346] "Copy files back to master node" doesn't copy to workspace

Aaron Simmons created issue - 2014-10-28 16:56

Aaron Simmons made changes - 2014-10-28 16:56

Description

Original: I've a matrix job that uses the "Copy To Slave" plugin to "Copy files back to master node" as a post-build action. I then use the PostBuildScript plugin to run on the master node to process these files. However, even though Copy-to-Slave succeeds, the files aren't in the master workspace. Look at the build output on the slaves shows: {code} [copy-to-slave] Copying 'build/**/*', excluding nothing, from 'file:/home/foobar/jenkins/workspace/JenkinsSandbox/label/foobar-ci-linux/' on 'hudson.slaves.DumbSlave@564c7adb' to 'file:/Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/' on the master. {code} The path {code} /Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/ {code} is not the workspace. The workspace is actually here: {code} /Users/foobar/.jenkins/.jenkins/workspace/JenkinsSandbox/ {code} Why does Copy-To-Slave copy the files to this weird path?

New: I've a matrix job that uses the "Copy To Slave" plugin to "Copy files back to master node" as a post-build action. I then use the PostBuildScript plugin to run on the master node and process these files. However, even though Copy-to-Slave succeeds, the files aren't in the master workspace. Look at the build output on the slaves shows: {code} [copy-to-slave] Copying 'build/**/*', excluding nothing, from 'file:/home/foobar/jenkins/workspace/JenkinsSandbox/label/foobar-ci-linux/' on 'hudson.slaves.DumbSlave@564c7adb' to 'file:/Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/' on the master. {code} The path {code} /Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/ {code} is not the workspace. The workspace is actually here: {code} /Users/foobar/.jenkins/.jenkins/workspace/JenkinsSandbox/ {code} Why does Copy-To-Slave copy the files to this weird path?

Aaron Simmons made changes - 2014-10-28 16:56

Description

Original: I've a matrix job that uses the "Copy To Slave" plugin to "Copy files back to master node" as a post-build action. I then use the PostBuildScript plugin to run on the master node and process these files. However, even though Copy-to-Slave succeeds, the files aren't in the master workspace. Look at the build output on the slaves shows: {code} [copy-to-slave] Copying 'build/**/*', excluding nothing, from 'file:/home/foobar/jenkins/workspace/JenkinsSandbox/label/foobar-ci-linux/' on 'hudson.slaves.DumbSlave@564c7adb' to 'file:/Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/' on the master. {code} The path {code} /Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/ {code} is not the workspace. The workspace is actually here: {code} /Users/foobar/.jenkins/.jenkins/workspace/JenkinsSandbox/ {code} Why does Copy-To-Slave copy the files to this weird path?

New: I've a matrix job that uses the "Copy To Slave" plugin to "Copy files back to master node" as a post-build action. I then use the PostBuildScript plugin to run on the master node and process these files. However, even though Copy-to-Slave succeeds, the files aren't in the master workspace. Looking at the build output on the slaves shows: {code} [copy-to-slave] Copying 'build/**/*', excluding nothing, from 'file:/home/foobar/jenkins/workspace/JenkinsSandbox/label/foobar-ci-linux/' on 'hudson.slaves.DumbSlave@564c7adb' to 'file:/Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/' on the master. {code} The path {code} /Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/ {code} is not the workspace. The workspace is actually here: {code} /Users/foobar/.jenkins/.jenkins/workspace/JenkinsSandbox/ {code} Why does Copy-To-Slave copy the files to this weird path?

Aaron Simmons made changes - 2014-10-28 16:57

Description

Original: I've a matrix job that uses the "Copy To Slave" plugin to "Copy files back to master node" as a post-build action. I then use the PostBuildScript plugin to run on the master node and process these files. However, even though Copy-to-Slave succeeds, the files aren't in the master workspace. Looking at the build output on the slaves shows: {code} [copy-to-slave] Copying 'build/**/*', excluding nothing, from 'file:/home/foobar/jenkins/workspace/JenkinsSandbox/label/foobar-ci-linux/' on 'hudson.slaves.DumbSlave@564c7adb' to 'file:/Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/' on the master. {code} The path {code} /Users/foobar/.jenkins/jobs/JenkinsSandbox/configurations/axis-label/foobar-ci-linux/workspace/ {code} is not the workspace. The workspace is actually here: {code} /Users/foobar/.jenkins/.jenkins/workspace/JenkinsSandbox/ {code} Why does Copy-To-Slave copy the files to this weird path?

New: I've a matrix job that uses the "Copy To Slave" plugin to "Copy files back to master node" as a post-build action. I then use the PostBuildScript plugin to run on the master node and process these files. However, even though Copy-to-Slave succeeds, the files aren't in the master workspace. Looking at the build output on the slaves shows: {code} [copy-to-slave] Copying 'build/**/*', excluding nothing, from 'file:/home/foobar/jenkins/workspace/MyJob/label/foobar-ci-linux/' on 'hudson.slaves.DumbSlave@564c7adb' to 'file:/Users/foobar/.jenkins/jobs/MyJob/configurations/axis-label/foobar-ci-linux/workspace/' on the master. {code} The path {code} /Users/foobar/.jenkins/jobs/MyJob/configurations/axis-label/foobar-ci-linux/workspace/ {code} is not the workspace. The workspace is actually here: {code} /Users/foobar/.jenkins/.jenkins/workspace/MyJob/ {code} Why does Copy-To-Slave copy the files to this weird path?

SCM/JIRA link daemon made changes - 2015-02-23 04:56

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

R. Tyler Croy made changes - 2016-07-25 23:56

Workflow

Original: JNJira [ 159266 ]

New: JNJira + In-Review [ 196036 ]