-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Windows
The Jenkins workspace is located on a file server. The file server is accessable via UNC. Git checkout works, but the maven parent resolving fails.
My git repository has the following structure:
backend parent-boot << parent of all backend projects pom.xml service << project to build pom.xml
the parent relationship is given as follows (service\pom.xml):
<parent> <groupId>com.my.project</groupId> <artifactId>backend.root</artifactId> <version>0.0.1-SNAPSHOT</version> <relativePath>../parent-boot</relativePath> </parent>
here the error message:
Baue in Arbeitsbereich \\FILESERVER-01\Repositories\Jenkins_Workspace\MASTER - com.my.projectBaue in Arbeitsbereich \\FILESERVER-01\Repositories\Jenkins_Workspace\MASTER - com.my.project The recommended git tool is: NONE No credentials specified > git.exe rev-parse --resolve-git-dir \\FILESERVER-01\Repositories\Jenkins_Workspace\MASTER - com.my.project\.git # timeout=10 Fetching changes from the remote Git repository > git.exe config remote.origin.url E:\My_Repositories\com.my.project # timeout=10 Fetching upstream changes from E:\My_Repositories\com.my.project > git.exe --version # timeout=10 > git --version # 'git version 2.22.0.windows.1' > git.exe fetch --tags --force --progress -- E:\My_Repositories\com.my.project +refs/heads/*:refs/remotes/origin/* # timeout=10 ... Parsing POMs ERROR: POMs konnten nicht geparst werden org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-readable POM E:\FILESERVER-01\Repositories\Jenkins_Workspace\MASTER - com.my.project\backend\parent-boot\pom.xml: E:\FILESERVER-01\Repositories\Jenkins_Workspace\MASTER - com.my.project\backend\parent-boot\pom.xml (Das System kann den angegebenen Pfad nicht finden) @ E:\FILESERVER-01\Repositories\Jenkins_Workspace\MASTER - com.my.project\backend\parent-boot\pom.xml at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:397) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:370) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:340) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1330) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1124) at hudson.FilePath.act(FilePath.java:1172) at hudson.FilePath.act(FilePath.java:1155) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:985) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:689) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:514) at hudson.model.Run.execute(Run.java:1888) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:99) at hudson.model.Executor.run(Executor.java:431)
It seems double backslash is replaced by "E:\" which is the drive Jenkins is installed on.