A week ago I asked about an issue where multiple builds were downloading to
the shared local repo and causing corruption in random jars.
My company's Jenkins team are offering the solution of running my own
private repo to avoid this, but this radically increases build times because
each build
Can I just verify the problem?
These affected jars are frequently used, and have been there for a long
time, e.g.
/home/jenkins/.m2/repository/commons-io/commons-io/2.4/commons-io-2.4.jar
There should be no writes going on to this or other affected jars by any
processes on the maven repo.
Are
For the record, it seems like the "EXECUTOR_NUMBER" variable (
https://issues.jenkins-ci.org/browse/JENKINS-31391 ) should be available to
be able to easily specify a per-executor repo.
So something such as this should do the job:
mvn -Dmaven.repo.local=$JENKINS_HOME/.m2/$EXECUTOR_NUMBER/ ...
I regularly have the same problem on my Jenkins build server: either
"corrupted zip file" or "cannot find symbol" and the only explanation for me
was concurrent build. I has never thought of having Maven local repo
specific to an executor, thanks Bernd Eckenfels, that's a really good point
!
I was
by only using deploy or have Jenkins deploy the
resulting artifacts After verify.
Gruss
Bernd
--
http://bernd.eckenfels.net
From: Adam Hardy <adam.ha...@cyberspaceroad.com>
Sent: Monday, March 26, 2018 7:44:17 PM
To: users@maven.apache.org
Subject: Not able to rea
What jars are you overwriting in your Maven repo? The SNAPSHOT system
allows things to be written in at the same time as other jobs depending on
the previous version.
Is this a problem with SNAPSHOT jars or non SNAPSHOT jars? It looks like
you're saying non SNAPSHOT:
I use a Jenkins server which is administered by another team. I get the
following errors intermittently. The team claim the issue is
"the maven repository is not multi write safe. It's possible several jobs are
updating the jar files at the same time and corrupt them. If that's the case,
the
