[ https://issues.jenkins-ci.org/browse/JENKINS-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159948#comment-159948 ]
Andy Bigos commented on JENKINS-8346: ------------------------------------- I have a similar problem with matrix configs. I'm copying the changelog.xml file into my workspace. So for a simple build I have: jobs/$JOB_NAME/builds/$BUILD_ID/changelog.xml with path set relative to HUDSON_HOME. This works for a simple project, however for a matrix project the $JOB_NAME gets expanded to the matrix element job name - this means the copy will fail as the source directory is not on the master. In the case of a matrix projects I think the plugin needs to use the 'base' project path, not the path for a matrix element. Can you confirm this is an issue? I can log it as new issue if you think it's different to the current issue. Thanks Andy > Copy to slave incompatible with multi configuration project > ----------------------------------------------------------- > > Key: JENKINS-8346 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8346 > Project: Jenkins > Issue Type: Bug > Components: copy-to-slave > Affects Versions: current > Reporter: psoetens > Assignee: Daniel Petisme > > copy-to-slave does nothing when the job runs on the master. This is the wrong > behavior if the job is a multi-configuration project, because these jobs run > with a modified workspace, depending on the parameter of the current job. > What the plugin should do when the job is running on the master, is to check > if the file in the 'default' workspace is identical to the target file (it > won't be in a multi-config build) and if not, copy it to the new workspace. > For example, the job on master has this workspace: > $ pwd > .../hudson/jobs/bootstrap-toolchain/workspace > $ ls > buildconf config-env.yml config.yml my-bootstrap.sh TARGET > where TARGET is the first category for the parametrization. The job will > never run in this 'workspace' dir, but somewhere deep in the TARGET subdir. > So copy-to-slave should copy the file from this workspace into the deep > 'multi-config' workspace. > For example, when my job runs, these variables are set: > JOB_NAME=bootstrap-toolchain/TARGET=gnulinux,arch=amd64,branch=master > WORKSPACE=.../hudson/jobs/bootstrap-toolchain/workspace/TARGET/gnulinux/arch/amd64/branch/master > I hope this report is clear about the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira