![]() |
|
|
|
|
Change By:
|
Aaron Simmons
(28/Oct/14 4:56 PM)
|
|
Description:
|
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
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?
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
