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

Default jar cache location is hardcoded to ~/.jenkins/cache/jars

    Details

    • Similar Issues:

      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

            Activity

            epkabeg Andréas Berg created issue -
            epkabeg Andréas Berg made changes -
            Field Original Value New Value
            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 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.
            epkabeg Andréas Berg made changes -
            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.
            epkabeg Andréas Berg made changes -
            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.
            joe_herbst Jörg Herbst made changes -
            Link This issue is related to JENKINS-18459 [ JENKINS-18459 ]
            kohsuke Kohsuke Kawaguchi made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Assignee Kohsuke Kawaguchi [ kohsuke ]
            Resolution Fixed [ 1 ]
            jglick Jesse Glick made changes -
            Resolution Fixed [ 1 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            jglick Jesse Glick made changes -
            Link This issue is related to JENKINS-18956 [ JENKINS-18956 ]
            jglick Jesse Glick made changes -
            Link This issue is related to JENKINS-20093 [ JENKINS-20093 ]
            jglick Jesse Glick made changes -
            Link This issue is related to JENKINS-22193 [ JENKINS-22193 ]
            jglick Jesse Glick made changes -
            Link This issue is blocking JENKINS-26199 [ JENKINS-26199 ]
            jglick Jesse Glick made changes -
            Labels cache configuration jenkins slave cache configuration robustness slave
            jglick Jesse Glick made changes -
            Assignee Kohsuke Kawaguchi [ kohsuke ] Oleg Nenashev [ oleg_nenashev ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 149885 ] JNJira + In-Review [ 186134 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Link JENKINS-37564 [ 173676 ]
            oleg_nenashev Oleg Nenashev made changes -
            Component/s remoting [ 15489 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Link JENKINS-37564 [ 173676 ] JENKINS-38833 [ 175240 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue is blocked by JENKINS-39370 [ JENKINS-39370 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue is blocking JENKINS-22239 [ JENKINS-22239 ]
            oleg_nenashev Oleg Nenashev made changes -
            Status Reopened [ 4 ] In Progress [ 3 ]
            oleg_nenashev Oleg Nenashev made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Link JENKINS-38833 [ 175240 ] JENKINS-44108 [ 181734 ]
            oleg_nenashev Oleg Nenashev made changes -
            Summary Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Default jar cache location is hardcoded to ~/.jenkins/cache/jars
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue depends on JENKINS-44973 [ JENKINS-44973 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue is duplicated by JENKINS-22239 [ JENKINS-22239 ]
            oleg_nenashev Oleg Nenashev made changes -
            Status In Review [ 10005 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            oleg_nenashev Oleg Nenashev made changes -
            Labels cache configuration robustness slave 2.60.2-rejected 2.60.3-rejected cache configuration robustness slave

              People

              • Assignee:
                oleg_nenashev Oleg Nenashev
                Reporter:
                epkabeg Andréas Berg
              • Votes:
                13 Vote for this issue
                Watchers:
                26 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: