[JIRA] (JENKINS-52657) [withMaven] IllegalArgumentException: Cannot relativize <some windows path> relatively to <some other windows path>

188 views
Skip to first unread message

mistafunk@java.net (JIRA)

unread,
Jul 19, 2018, 10:03:02 AM7/19/18
to jenkinsc...@googlegroups.com
mistafunk created an issue
 
Jenkins / Bug JENKINS-52657
[withMaven] IllegalArgumentException: Cannot relativize <some windows path> relatively to <some other windows path>
Issue Type: Bug Bug
Assignee: Alvaro Lobato
Components: pipeline-maven-plugin
Created: 2018-07-19 14:02
Environment: Windows 10, Jenkins LTS 2.121.1
Priority: Minor Minor
Reporter: mistafunk 
ERROR: [withMaven] WARNING Exception executing Maven reporter 'Open Task Scanner Publisher' / org.jenkinsci.plugins.pipeline.maven.publishers.TasksScannerPublisher. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org 
java.lang.IllegalArgumentException: Cannot relativize 'C:\data\jenkins\ws\cebjut\ce\com.esri\com.esri.master\src\main\java' relatively to 'C:/data/jenkins/ws/cebjut/ce/com.procedural.tests'
at org.jenkinsci.plugins.pipeline.maven.util.XmlUtils.getPathInWorkspace(XmlUtils.java:397)
at org.jenkinsci.plugins.pipeline.maven.publishers.TasksScannerPublisher.process(TasksScannerPublisher.java:134)
at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:118)
at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution.java:1050)
at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114)
at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:366)
at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:166)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122)
at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58)
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:332)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

mistafunk@java.net (JIRA)

unread,
Jul 19, 2018, 10:09:02 AM7/19/18
to jenkinsc...@googlegroups.com
mistafunk updated an issue
Change By: mistafunk
the task scanner seems tries to relativize a non-existing path... i guess that should be silent (even if if the maven build system does bad things)

 {code:java}
{code}

mistafunk@java.net (JIRA)

unread,
Jul 19, 2018, 10:10:01 AM7/19/18
to jenkinsc...@googlegroups.com
mistafunk updated an issue
the task scanner seems tries to relativize a non-existing path... i guess that should be silent (even if if the maven build system does bad things) ?

cleclerc@cloudbees.com (JIRA)

unread,
Jul 19, 2018, 7:06:03 PM7/19/18
to jenkinsc...@googlegroups.com

mistafunk@java.net (JIRA)

unread,
Jul 20, 2018, 4:58:02 AM7/20/18
to jenkinsc...@googlegroups.com

pipeline-maven-plugin 3.5.7, sorry i missed that

cleclerc@cloudbees.com (JIRA)

unread,
Jul 20, 2018, 8:29:01 AM7/20/18
to jenkinsc...@googlegroups.com
Cyrille Le Clerc assigned an issue to Cyrille Le Clerc
 
Change By: Cyrille Le Clerc
Assignee: Alvaro Lobato Cyrille Le Clerc

cleclerc@cloudbees.com (JIRA)

unread,
Jul 20, 2018, 8:29:01 AM7/20/18
to jenkinsc...@googlegroups.com
Cyrille Le Clerc updated an issue
Change By: Cyrille Le Clerc
Environment: Windows 10, Jenkins LTS 2.121.1 , pipeline-maven-plugin 3.5.7

cleclerc@cloudbees.com (JIRA)

unread,
Jul 20, 2018, 8:35:02 AM7/20/18
to jenkinsc...@googlegroups.com

cleclerc@cloudbees.com (JIRA)

unread,
Jul 29, 2018, 9:57:01 AM7/29/18
to jenkinsc...@googlegroups.com

mistafunk could you be invoking "withMaven(){}" from a folder that is not the root folder of your multi module maven project?

Can you do the following


dir ("path/to/maven-multi-module-root") {
   withMaven() {
      // if the desired pom.xml is at the root of the multi-module project
      sh "mvn clean verify"
      // if the desired pom.xml is NOT at the root of the multi-module project
      sh "mvn -f path/to/pom.xml clean verify"

   }
}

cleclerc@cloudbees.com (JIRA)

unread,
Sep 2, 2018, 5:26:02 PM9/2/18
to jenkinsc...@googlegroups.com
Cyrille Le Clerc started work on Bug JENKINS-52657
 
Change By: Cyrille Le Clerc
Status: Open In Progress
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

cleclerc@cloudbees.com (JIRA)

unread,
Sep 21, 2018, 11:05:01 AM9/21/18
to jenkinsc...@googlegroups.com

hello mistafunk, could you test the pattern of pipeline I proposed?

cleclerc@cloudbees.com (JIRA)

unread,
Jan 4, 2019, 8:23:01 AM1/4/19
to jenkinsc...@googlegroups.com
Cyrille Le Clerc stopped work on Bug JENKINS-52657
 
Change By: Cyrille Le Clerc
Status: In Progress Open
Reply all
Reply to author
Forward
0 new messages