That's what I was a 'fraid of. On Sun, Oct 25, 2009 at 6:04 PM, Stephen Connolly < [email protected]> wrote:
> it will result in chaos unless the parallel builds use orthogonal artifacts > (ie there are no interdependencies - if we ignore the version information) > > maven's local repo is not designed for parallel processes. there has been a > proposal to reorg the local repo and add locking, but it has not gathered > traction yet > > make sure you are using a repository manager on your local network and blow > away the local repo on each macine for each build... that is the safest way > to do CI > > Sent from my [rhymes with tryPod] ;-) > > > On 25 Oct 2009, at 21:53, Benson Margulies <[email protected]> wrote: > > We have an automated build process in which many build run in parallel on >> many machines. The user who runs the builds has a NFS home directory >> equally >> accessible from each. We're operating on the belief that adding maven to >> this build process will result in chaos (unless we force distinct local >> repos). However, it occurs to me maybe there is some appropriate use of >> file >> locking or some ordering of operations to render this viable? >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
