Hi!

I am migrating our build pipeline from a set of maven-type jobs to a
multi-branch project defined in a Jenkinsfile, and I am wondering how
people solve the .m2 problem ? I cannot see any way to configure every
job/branch to have its own private .m2 repo through a comfortable boolean
config option, did I miss something?

Otherwise I guess the solution is to set the .m2 path via
-Dmaven.repo.local. But how to best define this path so it is different for
every job/branch? Put it under /tmp/<GIT_BRANCH_NAME>? Any other more
elegant options?

Best regards,
 stefan.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CABwQARufwXt0gm7zmFfB-54pAipn1kNtbT5hpPVUgY%2B2Cza8tg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to