Am 2021-10-04 um 22:13 schrieb Francois Marot:
"Salut" Michael,
thanks for the detailled answer.
Regarding my Jenkins 'hack' you can totally forget about it: it just
ensures no more than one Maven execution uses a given repo at once by
locating the local repositories in a folder reflecting the executor (which
are kinda Jenkins "threads").
I plan not to use your work right now mostly because it would involve
setting up a Redis Database and my 'hack' still works (despite using a lot
of disk space and being a bit slow).
If I understand correctly after Tams' message, your work is mostly geared
toward running multiple Maven build in parallel and on multiple hosts, all
sharing one big "local" repository through the network. Am I correct ? In
my case, I have multiple Jenkins workers but never thought about making
them collaborate on a shared "local" repo. I'll have to think about it !
Not quite, we have multiple named locks which will give you the
granularity you need. Either in-JVM only, or multi-JVM. Then it does not
matter whether it is on the same host or not. You decide, the Redisson
approach will work. You need to read the docs how named locks are
discrimnated with a lock impl. That is all. You will benefit. User I was
talking about has now a huge speed bump due to the shared local repo,
for free.
M
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
