Wooohaa, thanks Thomas. It's a whole new world being revealed to me: I wasn't aware of the huge work happening on artifact resolvers. At the same time, it seems not to be available out of the box (needs a Redis server) so I'll keep my Jenkinsfile hacks for now and will wait for proper documentation and how-to. Thanks for the pointers !
*François Marot* Le lun. 4 oct. 2021 à 15:10, Thomas Broyer <t.bro...@gmail.com> a écrit : > From JIRA links, this is apparently fixed by > https://issues.apache.org/jira/browse/MRESOLVER-131, which means you need > to deploy a Redis server. > There apparently also is an Hazelcast-based version: > https://maven.apache.org/resolver/maven-resolver-named-locks/index.html > > On Mon, Oct 4, 2021 at 2:32 PM Francois Marot <francois.ma...@gmail.com> > wrote: > > > Hello all, > > > > I would like clarifications on MNG-2802[*] that seems to be solved. If I > > understand correctly it solves the problem where multiple simultaneous > > Maven executions shared the same local repository. > > I have been keeping for years a bit of code in my Jenkinsfiles ensuring > the > > local repos were accessed only by a single jenkins executor at the same > > time, so it seems like I can get rid of this doesn't it ? > > I'd like your input on this because reproducing the bug is difficult so > I'd > > like to be sure before simplifying my Jenkinsfile. > > > > Moreover, does anyone know how this problem is solved technically ? Using > > files lock ? Can anybody explain ? > > > > Thanks you and thanks the Maven team for keeping up the good work at such > > pace ! > > > > François MAROT > > > > > > * https://issues.apache.org/jira/browse/MNG-2802 > > > > > -- > Thomas Broyer > /tɔ.ma.bʁwa.je/ <http://xn--nna.ma.xn--bwa-xxb.je/> < > http://xn--nna.ma.xn--bwa-xxb.je/> >
