> > If you are knowingly doing this then I would say different settings > via a build plan to prevent corruption or the CI mechanism serializes > the builds. >
How can one do this and still make use of all 8 cores to build on a desktop machine (or all 16 on our CI server)? m2 builds could run really parallel, but they frequently break when they do (particularly when one buildl downloads a plugin, and another one uses it half-way through, getting wrong metadata). Is there a way of serializing access to the local repository? This seems a really important feature given the way computers are rapidly adding cores. m2 has the intelligence to know what things can be parallelized because of its smart dependency mechanism, but it falls down because of the dumb local repo into an antlike serial process. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
