Florian a workaround is to use environment variables :

  • Go to Jenkins > Manage Jenkins > Configure
  • In the Global properties section define an environment variable that references the path for the root of your workspace. It will need to be an absolute path.
    example: MYMATRIXWS C:\MyMatrix\jobs
  • Go to Jenkins > Manage Jenkins > Manage Nodes choose your slave node choose Configure
  • In the Node properties section define the same environment variable again, but reference the path for the root of your workspace on the node. It will need to be an absolute path.
    example: MYMATRIXWS C:\MySlaveMatrix\jobs
  • Go to Jenkins > Jobs choose your job choose Configure
  • In the section "Advanced Project Options" click the advanced settings button
  • Check the box "Use custom workspace" it will expand a section to supply workspace paths for the main build and the sub-builds.
  • In the "Directory" textbox, put in your environment variable followed by a directory in which to load for the main build.
    example: ${MYMATRIXWS}/workspace/mainJob

    - In the "Directory for sub-builds" textbox, put in your environment variable followed any subdirectory minus the directory for the main build, followed by /${JOB_NAME}
    example: ${MYMATRIXWS}/workspace/${JOB_NAME}
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to