Sometimes the JAR caching causes significant issues (e.g. JENKINS-20913). It would be great to have a CLI option, which completely disables the caching on the node.

          [JENKINS-22193] Add an option to disable the Jar caching

          Jesse Glick added a comment -

          Seems like a fix of JENKINS-18578 would solve that kind of issue in a better way. Why not work on that instead of disabling JAR caching altogether?

          Jesse Glick added a comment - Seems like a fix of JENKINS-18578 would solve that kind of issue in a better way. Why not work on that instead of disabling JAR caching altogether?

          Daniel Beck added a comment - - edited

          IMO this could be resolved as duplicate of JENKINS-18578. A safe location should always be available in the slave home path...

          Daniel Beck added a comment - - edited IMO this could be resolved as duplicate of JENKINS-18578 . A safe location should always be available in the slave home path...

          Oleg Nenashev added a comment -

          Caching sometimes leads to locked files (see JENKINS-20913).
          BTW, I don't see failures in newest core version => the priority can be decreased

          Oleg Nenashev added a comment - Caching sometimes leads to locked files (see JENKINS-20913 ). BTW, I don't see failures in newest core version => the priority can be decreased

          Oleg Nenashev added a comment -

          Closing in favor of JENKINS-18578

          Oleg Nenashev added a comment - Closing in favor of JENKINS-18578

            oleg_nenashev Oleg Nenashev
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: