I regularly suffer from corrupted maven-metadata-local.xml files on my
Jenkins host in directory /home/jenkins/.m2/.../some-project/
E.g. extra lines added to the end of the maven-metadata-local.xml file like
this:
...
astUpdated>
Do I suffer from concurrency issues? Like the one describ
Hi,
On 09.05.19 16:09, Frizz wrote:
I regularly suffer from corrupted maven-metadata-local.xml files on my
Jenkins host in directory /home/jenkins/.m2/.../some-project/
I suppose you are using the local cache for all your jobs?
If so this is the problem. The cache is and was intended for r
IME, the default settings for plugins in Jenkins are sometimes objectively
incorrect. One example is the setting Karl referred to. More specifically,
if you are using the Maven plugin for Jenkins, got to your job config ->
Build -> Advanced -> Use private Maven repository. The default setting of
us
Hello, I suffered from similar symptoms until I adjusted the build to have
per-Jenkins-executor MAven cache. So in the end, my Maven configuration in
my Jenkins pipeline looks like this:
As you can see, I do not use any Jenkins-Maven plugin and Maven is
configured by hand. Hope it may help
--
Sorry, seems my previous message missed the copy pasted content ! Here it is:
pipeline {
agent { node { label paramsMap.agentParam } }// the build will
only run on nodes (ie slaves) indicated
environment {
// To prevent simultaneous job working in the same Mave
There was one more email with the same problem.
We are talking about this problem, global repo:
'$COMPANY_JENKINS_HOME.m2/repository/executor_$EXECUTOR_NUMBER'
Our build creates pwd() + "/.m2" in the job, and the scm checkouts git repo
to "./build" directory.
No issue then!
The Jenkinsfile should
