Thank you, point taken and thanks for correcting the terminology (local maven repo -> m2 cache) - I wanted to get a feedback on another related question/clarification with a follow up (this might be more of a maven/nexus question) :
We use Nexus as our snapshot and release repositories; If we instruct all of our maven installations (on each slave) to download everything from nexus (i.e. like this<https://support.sonatype.com/entries/20943003-Configure-Maven-to-Download-from-Nexus>), would Jenkins+Maven-plugin effectively now use nexus as its local maven repo (cache), or local m2. checks will always happen before going to remote nexus? appreciate the feedback. --Seena On Saturday, February 22, 2014 9:59:45 AM UTC-5, Baptiste Mathus wrote: > > This is actually unsafe. You take the risk to corrupt the "maven local > repository" (badly named, think more about it like a cache). And there's > also potential issues of having a stale dependency installed in the local > cache/repository (and if it's not a snapshot, it will never be downloaded > again unless you delete it). > > In your case, as you're likely to have many executors per slave (which btw > i wouldn't recommend) the probability to corrupt the cache is even bigger. > Then, on top of that, using NFS increases the risk even more, since (your > executors count) processes will access the cache concurrently. > > Having a 'private' repository and cleaning it up on a regular basis is in > fact simple and quite straightforward. The only downside is the disk space, > but as having more disks is certainly cheaper than spending time to debug > corrupted repository issues. > > Hth > Le 21 févr. 2014 17:08, "Seena Kasmai" <see...@gmail.com <javascript:>> a > écrit : > >> Greetings - >> >> It seems there is an outstanding maven issue "Concurrent-safe access to >> local Maven repository <http://jira.codehaus.org/browse/MNG-2802>" which >> would advise against setting up all Jenkins servers to use a shared (e.g >> NFS mount) maven local repo - Can anyone confirm or share experience on how >> unsafe this would be? >> >> The issue with having different repo is managing the cleaning up for each >> and also not optimized when running same job in different slaves, all maven >> artifacts have to be republished etc...(this is for a setup of 1000s of >> jobs across 10 slaves) >> >> Any suggestions/advise would be helpful. >> >> Thanks, >> --Seena >> >> -- >> 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 jenkinsci-use...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
