-
Bug
-
Resolution: Won't Fix
-
Critical
-
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).