|
||||||||
|
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.

Hi!
I have run some tests to determine additional information on this issue:
1. Global configuration:
Custom tool installation "gcc-4.9.2-i386" as ZIP-Download; Sub-directory of extracted archives = bin (Ie. sub-folder of executable).
Overriden (global) tool-location of "(Custom tool" gcc-4.9.2-i386"): Home = C:\tools\master\gcc-4.9.2-i386
2. Addition slave 'SLAVE1', with
tool-location of "(Custom tool) gcc-4.9.2-i386": Home = C:\slave\tools\gcc-4.9.2-i386
A) If a job (with installing this tool) runs on master, following occurs
(in not already done)
Note: The (global) configured tool-location isn't used.
B) If the same job run on a slave (Ie. SLAVE1, configured as written above), following occurs:
As result of the configured tool-location (for this tool on a slave):
Based on these tests, my personal conclusio is: Don't configure a tool location;
to "enforce" a similar behavior (+ automatic installation) on master and slave(s).
Maybe the feature-request as describe in https://issues.jenkins-ci.org/browse/JENKINS-27158 can be implemented in a future release:
Optionally disabling add of HOME-directory to PATH-variable (but that's my personal opinion/wish).
BR,
Markus