Automated Build Generator

Seriously? It is not possible to execute more than one maven build in parallel on the same machine (can different users use maven in parallel on the same machine?)?

If true, this has far-reaching consequences beyond generating a restricted build-flow. Consider citoolkit, for example. With this restriction, we basically cannot have more than one distribution on that Jekins instance unless we resort to some locking strategy. But what would the scope of such a lock be, in general? The whole Jenkins instance? A particular slave?

Jan Moringen wrote:

Seriously? It is not possible to execute more than one maven build in parallel on the same machine (can different users use maven in parallel on the same machine?)?

Normally it works but there is no guarantee that things work correctly due to the .m2/repository folder which would then be changed in parallel by several processes, which might lead to inconsistencies. Multiple users can operate in parallel since everyone has got its own cache.

If true, this has far-reaching consequences beyond generating a restricted build-flow. Consider citoolkit, for example. With this restriction, we basically cannot have more than one distribution on that Jekins instance unless we resort to some locking strategy. But what would the scope of such a lock be, in general? The whole Jenkins instance? A particular slave?

Beyond the scope of one distribution this is even harder. Sure. But maybe we can first generate the build flow in a way that this is respected. The triggering of different distributions can in the first step be sequenced by timing their build correctly.