Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: Major
Component/s: core, remoting
Labels:
Environment:
N/A

Similar Issues:

Show
Epic Link:
Remoting Work Directory Support

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.

depends on

JENKINS-44973 Remoting tests crash when running on Socket or STDOUT/STDERR without Workspace

Resolved

is blocked by

JENKINS-39370 Introduce the remoting working directory concept

Resolved

is blocking

JENKINS-22239 Doesn't create root folder when installing JNLP Windows Service

Resolved

JENKINS-26199 CpsScriptTest.evaluateShallBeCpsTransformed failures

Resolved

is duplicated by

JENKINS-22239 Doesn't create root folder when installing JNLP Windows Service

Resolved

is related to

JENKINS-18956 Cache location should be configurable through the GUI

Open

JENKINS-18459 IOException: No Such File

Resolved

JENKINS-20093 Start JNLP slave ignores jar-cache flag

Resolved

JENKINS-22193 Add an option to disable the Jar caching

Resolved

(4 is related to)

Assignee:: Oleg Nenashev

Reporter:: Andréas Berg

Votes:: 13 Vote for this issue

Watchers:: 27 Start watching this issue

Created:: 2013-07-02 11:13

Updated:: 2017-07-07 09:52

Resolved:: 2017-07-01 05:59

Details

Description

Attachments

Issue Links

Activity

People

Dates