Status: Open (View Workflow)
This is a follow-up to
The cache location should be configurable through the GUI. "Launch slave agents on Unix machines via SSH" does not allow specifying -jar-cache so we are expected to manually edit the machine configuration by hand, making it a maintenance nightmare.
If this configuration were configurable by GUI, we could create a Slave "template" and copy it when creating new nodes.
- is related to
JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars
Is there a way to use the command line parameter on the master node?
The issue that I have is that it still creates the cache folder with jars even when JENKINS_HOME is set to another directory.
I concur, the jar cache location needs to be configurable. While is is great to be able to change the location from the command line for slaves, this needs to be available for masters/standalone configurations.
Another workaround I've found that worked better for me both on master and slave is changing the `user.home` System property by setting the `_JAVA_OPTIONS` environment variable as described [here](http://stackoverflow.com/questions/1501235/change-user-home-system-property).
Edit the Suffix Start Slave Command under Advanced and specify e.g. -jar-cache /path/to/jars (with a leading space). Not a convenient button to click, but gets the job done.