![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
02/Jul/13 11:13 AM
|
|
Description:
|
The default jar cache location is now hardcoded to ~/.jenkins/cache/jars which is a really bad idea for a big production environment with networked home directories and multiple accounts running slaves.
This behaviour was introduced with this commit:
https://github.com/jenkinsci/remoting/commit/b5145a06876f4390ef3229d70fa5a7edf0739dae
This cache location needs to be configurable.
A bonus would be if permissions within it were handled in a way that supports multi accounts using it. That might be the case already though.
We've put a workaround in place by defining "-Duser.home" to java but that affects other things too. It also needs to be done for master and every slave seperately so it is easy to make misstakes or forget it for some slaves.
|
|
Environment:
|
N/A
|
|
Project:
|
Jenkins
|
|
Labels:
|
jenkins
configuration
slave
cache
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Andréas Berg
|
|
|
|
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.
