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
-
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
-
Code changed in jenkins
User: Oleg Nenashev
Path:
src/main/java/hudson/remoting/Launcher.java
http://jenkins-ci.org/commit/remoting/a547765c8b9cca411c2db999b53074aa2ed8d9d9
Log:
JENKINS-18578- Do not use the old cache when starting agents from CLIJust a leftover from the previous fix, nulls are handled in hudson.remoting.Engine.