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
Hi,
Don't know Gradle well at all, but I'm even surprised it can be used with
the Jenkins maven plugin...
Anyway, in the Maven world, what you ask is not recommended (even the
contrary).
The normal practice would be to push (deploy in maven terms) your
artifacts onto a central and local
