Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
N/A
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 multiple accounts using it. That might be the case already though.
Attachments
Issue Links
- depends on
-
-
- Resolved
-
- is blocked by
-
JENKINS-39370 Introduce the remoting working directory concept
-
- Resolved
-
- is blocking
-
-
- Resolved
-
-
JENKINS-26199 CpsScriptTest.evaluateShallBeCpsTransformed failures
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-
- is related to
-
JENKINS-18956 Cache location should be configurable through the GUI
-
- Open
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
(4 is related to)
Activity
| Field | Original Value | New Value |
|---|---|---|
| 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. |
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 tried to put a workaround in place by defining "-Duser.home" to java but that affects other things too and even when done for master and every slave seperately it does not get rid of the behaviour. |
| Issue Type | Improvement [ 4 ] | Bug [ 1 ] |
| Priority | Minor [ 4 ] | Major [ 3 ] |
| 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 tried to put a workaround in place by defining "-Duser.home" to java but that affects other things too and even when done for master and every slave seperately it does not get rid of the behaviour. |
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 tried to put a workaround in place by defining "-Duser.home" to java but that affects other things too and even when done for master and every slave seperately I am not sure if it solves the problem entirely. |
| 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 tried to put a workaround in place by defining "-Duser.home" to java but that affects other things too and even when done for master and every slave seperately I am not sure if it solves the problem entirely. |
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 multiple accounts using it. That might be the case already though. |
Jörg Herbst
made changes -
| Link |
This issue is related to |
| Assignee | Kohsuke Kawaguchi [ kohsuke ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Link | This issue is related to JENKINS-18956 [ JENKINS-18956 ] |
| Link |
This issue is related to |
| Link |
This issue is related to |
| Link |
This issue is blocking |
| Labels | cache configuration jenkins slave | cache configuration robustness slave |
| Assignee | Kohsuke Kawaguchi [ kohsuke ] | Oleg Nenashev [ oleg_nenashev ] |
| Workflow | JNJira [ 149885 ] | JNJira + In-Review [ 186134 ] |
| Epic Link |
|
| Component/s | remoting [ 15489 ] |
| Epic Link |
|
JENKINS-38833 [ 175240 ] |
| Link |
This issue is blocked by |
| Link |
This issue is blocking |
| Status | Reopened [ 4 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | In Review [ 10005 ] |
| Epic Link | JENKINS-38833 [ 175240 ] | JENKINS-44108 [ 181734 ] |
| Summary | Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable | Default jar cache location is hardcoded to ~/.jenkins/cache/jars |
| Link |
This issue depends on |
| Link |
This issue is duplicated by |
| Resolution | Fixed [ 1 ] | |
| Status | In Review [ 10005 ] | Resolved [ 5 ] |
| Labels | cache configuration robustness slave | 2.60.2-rejected 2.60.3-rejected cache configuration robustness slave |