|
||||||||
|
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.
Unfortunately, no I haven't found any other workarounds. Environment variables for the build itself did not seem to be available to Jenkins in the deciding the workspace path. Only thing I can think of is defining environment variables in the environment that Jenkins runs in and seeing if they are substituted in the calculation of the workspace path. If that worked, setting it in the slave environment and the master environment might be an option.