I've got a case where we get random CI build failures. The error is:
[FATAL] Non-resolvable parent POM: Could not find artifact
com.issinc.jms.jms-thirdparty.installers:installer-parent:pom:11.8.0-SNAPSHOT
in nexus (https://mavenserver/nexus/content/groups/public) and
'parent.relativePath'
Hi Dave,
Maven is not safe for concurrent builds from the same local repository
cache. Do these CI jobs share the same cache? If so that would explain the
nondeterminism you are seeing.
It is best practice if each job has its own local repo cache, as expensive
as that is disk-wise.
Or you can
Another solution is to try the Takari.io extensions. One of them has
filesystem locks on the local repo for exactly this scenario. I haven't tried
these out on our CI pipeline yet, though.
Takari | Team-maven
| |
| | | | | |
| Takari | Team-mavenTakari is focused on continuous
Wow that got mangled. Let's try that link again:
http://takari.io/book/30-team-maven.html
-- Larry Bordowitz
On Thursday, July 30, 2015 9:58 AM, Laurence Bordowitz
lbordow...@yahoo-inc.com.INVALID wrote:
Another solution is to try the Takari.io extensions. One of them has
Hi Curtis,
To answer your first question...we have lots of build agents...each agent
will run one build at a time. That agent will share a local repo with
other builds that happen to run on the same agent but it's sequential
nothing concurrent ever happens in the CI build.
Regarding why this
