Hi again, I tried to reproduce the fault with more logs, but I'm not able to do that. So I guess the problem is related to when I try to uplift the parent in many project at the same time.
So it might be that the .m2 get corrupt for the snapshot version, but I have never seen the same issue when I do the same for regular releases. I have 30 servers, and each of them have it is own .m2 repository, but I allow 3 executors per server, so 3 jobs can share the same local repository. Maybe I must have a local repository per Jenkins executor. Regards /Martin On October 3, 2021 at 11:52:35 pm +02:00, Hervé BOUTEMY <[email protected]> wrote: > can you please share the <parent><version>xxx</version> part of your pom.xml, > please? > > and look at logs of "mvn -X", to see precisely what urls are fetched? > > Regards, > > Hervé > > Le samedi 2 octobre 2021, 10:58:14 CEST Martin Aldrin a écrit : > > > Hi, thanks for the answer. > > > > 1. We have used this format for years in our CI. And it works perfect for > > all other dependencies. > > > > 2. Yes, the artifact exist on our nexus server. And it works perfect if I > > first fetch it to my local repository. > > > > Regards > > /Martin > > > > > > > On 2 Oct 2021, at 09:53, Hervé BOUTEMY <<[email protected]>> wrote: > > > > > > Hi Martin, > > > > > > I'm replying to <[email protected]> because > > > <[email protected]> is > > > not a mailing list where anybody answers :) > > > > > > Looking at the log, I see "Could not find artifact com.x.commonlibrary:cl- > > > parent:pom:1.5.39-20210922124845805-SNAPSHOT" > > > > > > It seems you referenced parent POM as "1.5.39-20210922124845805-SNAPSHOT" > > > when: > > > 1. you should not add the "-SNAPSHOT" suffix but > > > "1.5.39-20210922124845805": Maven detects that the suffix represents a > > > SNAPSHOT > > > 2. are you sure of your "-20210922124845805" value, as it is represented > > > in > > > your repository? With usual format (that I think is the only one > > > supported), it should be "-20210922.124845-805" > > > > > > Regards, > > > > > > Hervé > > > > > > Le vendredi 1 octobre 2021, 13:46:42 CEST <[email protected]> a écrit : > > > > > > > Hi, > > > > My problem is that I want to test uplift our parent on 400 project to > > > > test > > > > the combability with Java 17 without releasing the new parent. It works > > > > perfect for regular releases, but not if I using a snapshot with time > > > > prefix. Do any one have a idea if this can be solved in any way or if > > > > I'm > > > > doing something wrong. It works if first trigger a download of the > > > > snapshot > > > > artifact, but I don't want to do that manually on all different servers, > > > > I > > > > hope the snapshot could be downloaded automatically as it works for > > > > regular > > > > dependencies. > > > > > > > > > > > > > > > > mvn -U help:evaluate -f pom.xml -Dexpression=project.properties > > > > Exit Code: 1[Pipeline]ech)Warning: A secret was passed to "echo" using > > > > Groovy String interpolation, which is insecure. Affected argument(s) > > > > used > > > > the following variable(s):[FUNCTIONAL_CRED_USR] > > > > See[<<https://jenkins.io/redirect/groovy-string-interpolatio>>|<https://jen > > > > ki > > > > ns.io/redirect/groovy-string-interpolation]n> for details. Output: ----- > > > > withMaven Wrapper script ----- > > > > Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) > > > > Maven home: /app/vbuild/tools/maven/3.6.3 > > > > Java version: 17, vendor: Azul Systems, Inc., runtime: > > > > /app/openjdk/17.0.0 > > > > Default locale: en_US, platform encoding: ISO-8859-1 > > > > OS name: "linux", version: "3.10.0-1127.el7.x86_64", arch: "amd64", > > > > family: > > > > "unix" [INFO][jenkins-event-spy]Generate > > > > maven-spy-20210923-121848-99516578763949166347886.log.tmp ... > > > > [INFO]Scanning for projects...[ERROR][ERROR]Some problems were > > > > encountered > > > > while processing the POMs:[FATAL]Non-resolvable parent POM for > > > > com.x.commonlibrary:test-suite-editor:0.2.115-SNAPSHOT: Could not find > > > > artifact > > > > com.x.commonlibrary:cl-parent:pom:1.5.39-20210922124845805-SNAPSHOT and > > > > 'parent.relativePath' points at wrong local POM @ line 9, column 13 @ > > > > [INFO][jenkins-event-spy]Generated > > > > maven-spy-20210923-121848-99516578763949166347886.log[ERROR]The build > > > > could > > > > not read 1 project ->[Help 1][ERROR][ERROR]The project > > > > com.x.commonlibrary:test-suite-editor:0.2.115-SNAPSHOT > > > > /proj/cl1/pom.xml) > > > > has 1 error[ERROR]Non-resolvable parent POM for > > > > com.x.commonlibrary:test-suite-editor:0.2.115-SNAPSHOT: Could not find > > > > artifact > > > > com.x.commonlibrary:cl-parent:pom:1.5.39-20210922124845805-SNAPSHOT and > > > > 'parent.relativePath' points at wrong local POM @ line 9, column 13 > > > > ->[Help > > > > 2][ERROR][ERROR]To see the full stack trace of the errors, re-run Maven > > > > with the -e switch.[ERROR]Re-run Maven using the -X switch to enable > > > > full > > > > debug logging.[ERROR][ERROR]For more information about the errors and > > > > possible solutions, please read the following articles:[ERROR][Help > > > > 1][<<http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingExcep> > > > > ti > > > > o>|<<http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingExcep> > > > > tio n]n[ERROR>][Help > > > > 2][<<http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelExc> > > > > ep > > > > tio>|<<http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelE> > > > > xce ption]n> > > > > > > >
