|
||||||||
|
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/d/optout.
Hi!
Yes, I've run the (test-) job on the master!
To understand my use-case:
Currently, we are using a variable like "JOBS_WORKS_ROOT", which is defined for the master and each slave (specific). This variable defines the root-directory which contains (at least) all wokspaces. The (main-) tools are located under ${JOBS_WORKS_ROOT}\shared\tools\<tool-name> and each job - regardless whether it runs on the master or an a slave - can use use these "relative" setup of tools.
My idea was, to configure "${JOBS_WORKS_ROOT}\shared\tools\<tool-name>" as home location to get the same behaviour (but with automatic download and installation).
Up to now, I've not tested, whether the location-override has an effect on slaves![]()
As work-around I've already determined, that a (hard) directoy-link does redirect the installation to get a similar behaviour.
Best regards from Salzburg,
Markus