Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-18956

Cache location should be configurable through the GUI

    XMLWordPrintable

Details

    • Improvement
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • core
    • None

    Description

      This is a follow-up to JENKINS-18578.

      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.

      Attachments

        Issue Links

          Activity

            danielbeck Daniel Beck added a comment - - edited

            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.

            danielbeck Daniel Beck added a comment - - edited 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.
            roastlechon Noel Madali added a comment -

            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.

            roastlechon Noel Madali added a comment - 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.

            robert_greathouse Robert Greathouse added a comment - 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).

            randroid Roberto Andrade added a comment - 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 ).

            People

              Unassigned Unassigned
              cowwoc cowwoc
              Votes:
              7 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated: