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

Maven local repository should be settable to workspace location

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Critical Critical
    • gradle-plugin
    • None

      At the moment all jobs write their artifacts to the Maven repository in the build user's home directory (~/.m2).
      This is a big problem when there are lots of builds:

      • the disk is filled up with lots of data (/home is usually not on a remote SAN/NAS storage)
      • builds can access artifacts of other builds which can result in strange situations

      Suggestion: There should be an option where the local Maven repo is located just like the Jenkins Maven plugin does ("Local Maven Repository" option).

          [JENKINS-19407] Maven local repository should be settable to workspace location

          George Simpson added a comment -

          Not sure this is a bug. Feels like a feature request. Also not clear to me that having good support for Maven from the gradle plugin is a useful thing. Unless someone has a differing opinion, will close this issue as won't fix.

          George Simpson added a comment - Not sure this is a bug. Feels like a feature request. Also not clear to me that having good support for Maven from the gradle plugin is a useful thing. Unless someone has a differing opinion, will close this issue as won't fix.

          Stefan Wolf added a comment -

          I second gsimpson's opinion - so closing as won't fix.

          Stefan Wolf added a comment - I second gsimpson 's opinion - so closing as won't fix.

            gbois Gregory Boissinot
            gruberrolandfiducia Roland Gruber
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: