Yes, I use the approach you mentioned, it works perfectly. The
ivysettings.xml snippet:
<properties environment="env" />
<caches
defaultCacheDir="${ivy.cache.dir}-${env.EXECUTOR_NUMBER}"
ivyPattern="${default.ivy.pattern}"
artifactPattern="${default.artifact.pattern}" />
On Wed, Aug 22, 2012 at 8:12 PM, David Weintraub <qazw...@gmail.com> wrote:
>
> I was thinking somehow to include the Jenkins Executor Number to
> eliminate this conflict. I might end up with multiple local
> repositories, but it would eliminate the concurrency issue. If I
> somehow incorporate the Executor Number as part of the ivy repository
> location, then if Executor #1 is running and does an <ivy:cleancache>,
> it won't affect any other job that might be currently running.
>
> --
> David Weintraub
> qazw...@gmail.com
>
