![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Gregory Boissinot
|
|
Components:
|
shared-objects |
|
Created:
|
30/Jul/12 11:30 PM
|
|
Description:
|
When using the Populate Tools Installations option the SharedObjects plugin goes and tries to install ALL the tools defined globally. The result is that a proliferation of mavens, or JDKs, or Git, get installed on the slave where the job runs.
In some cases, and depending on the way some tools are installed, the practice of installing several versions of the same tool may lead to undesirable effects – making this plugin harmful in this context and hence banned (unfortunately).
Instead of installing ALL versions of ALL tools, the plugin should install only the tools/versions specified by the job. When selected, the Populate Tools Installations toggle should be expanded with the list of all tools/versions available, with a selection box for each. See the Tool Environment plugin for a good example of the desired functionality (http://wiki.hudson-ci.org/display/HUDSON/Tool+Environment+Plugin).
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Patrick Renaud
|
|
|
|
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
|
