We have a bunch of gradle jobs that are build with the maven plugin meaning that the build artifacts gets deployed to the local .m2 repo. On Jenkins we have added 4 slaves each with its own .m2 repo.
We have two projects A and B where B depends on A. If A gets build on slave2 and B gets build on slave1 B fails since it cannot see A in its local .m2 repo (we are still in the process of setting up deployment to a repository manager but need our builds to work until then). Is it possible for build jobs to consider/read across .m2 repos on all slaves but only deploy to its own .m2? Alternatively setting up a global .m2 for all slaves to use. Should be rather trivial but to my understanding also more risky - concurrent access issues? -- View this message in context: http://jenkins.361315.n4.nabble.com/m2-repository-on-slave1-not-visible-when-building-with-slave2-tp4642005.html Sent from the Jenkins users mailing list archive at Nabble.com.
