The function withMaven() fails after the Maven build has finished in Jenkinsfile

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

The function withMaven() fails after the Maven build has finished in Jenkinsfile

Tibor Digana
Please check logs of build process.
I have got BUILD SUCCESS of Maven run but the function *withMaven()* fails
right after the Maven process has finished. I have no idea why.

Because of this call in the stacktrace

*WithMavenStepExecution$WorkspaceCleanupCallback.finished*

I guess the function *withMaven()* is still doing something much later when
*cleanWs()* finished.

The principle looks like this:


*try {*

*    withMaven()*

*} finally {*

*    cleanWs()*
*}*

This is the stacktrace:

[windows] [INFO] BUILD SUCCESS
[windows] [INFO]
------------------------------------------------------------------------
[windows] [INFO] Total time: 43:08 min
[windows] [INFO] Finished at: 2018-02-18T04:34:10+00:00
[windows] [INFO] Final Memory: 48M/161M
[windows] [INFO]
------------------------------------------------------------------------
[windows] [INFO] [jenkins-event-spy] Generated
F:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp
\withMavene898fc1f\maven-spy-20180218-035101-1877982869374894449694.log
[windows] Picked up JAVA_TOOL_OPTIONS:
-Dmaven.ext.class.path="f:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp\withMavene898fc1f\pipeline-maven-spy.jar"
-Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="f:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp\withMavene898fc1f"

[Pipeline] [windows] }
[windows] ERROR: [withMaven] WARNING Exception processing the logs
generated by the Jenkins Maven Event Spy
f:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp\withMavene898fc1f\maven-spy-20180218-042026-3958838718902276550716.log,
ignore file.  Please report a bug associated for the component
'pipeline-maven-plugin' at https://issues.jenkins-ci.org
[windows] java.lang.InterruptedException
[windows]     at java.lang.Object.wait(Native Method)
[windows]     at hudson.remoting.Request.call(Request.java:167)
[windows]     at hudson.remoting.Channel.call(Channel.java:907)
[windows]     at hudson.FilePath.act(FilePath.java:986)
[windows]     at hudson.FilePath.act(FilePath.java:975)
[windows]     at hudson.FilePath.exists(FilePath.java:1440)
[windows]     at
org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:105)
[windows]     at
org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WorkspaceCleanupCallback.finished(WithMavenStepExecution.java:1015)
[windows]     at
org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114)
[windows]     at
org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:368)
[windows]     at
com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73)
[windows]     at
com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:166)
[windows]     at
com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
[windows]     at
org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122)
[windows]     at
org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261)
[windows]     at
com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
[windows]     at
org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:19)
[windows]     at
org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:35)
[windows]     at
org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:32)
[windows]     at
org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)
[windows]     at
org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:32)
[windows]     at
org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174)
[windows]     at
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:331)
[windows]     at
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:82)
[windows]     at
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:243)
[windows]     at
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:231)
[windows]     at
org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64)
[windows]     at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[windows]     at
hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
[windows]     at
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
[windows]     at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[windows]     at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[windows]     at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[windows]     at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[windows]     at java.lang.Thread.run(Thread.java:748)
Reply | Threaded
Open this post in threaded view
|

Re: The function withMaven() fails after the Maven build has finished in Jenkinsfile

Tibor Digana
Hi Stephen,

I reported the issue [1] and assigned to Cyrille.

[1]: https://issues.jenkins-ci.org/browse/JENKINS-49614

Cheers
Tibor



On Sun, Feb 18, 2018 at 5:54 PM, Stephen Connolly <
[hidden email]> wrote:

> Can you file an issue against the pipeline-Maven-plugin @ Jenkins (and
> maybe try pinging Cyrille on Twitter)
>
> On Sun 18 Feb 2018 at 16:16, Tibor Digana <[hidden email]> wrote:
>
> > Please check logs of build process.
> > I have got BUILD SUCCESS of Maven run but the function *withMaven()*
> fails
> > right after the Maven process has finished. I have no idea why.
> >
> > Because of this call in the stacktrace
> >
> > *WithMavenStepExecution$WorkspaceCleanupCallback.finished*
> >
> > I guess the function *withMaven()* is still doing something much later
> when
> > *cleanWs()* finished.
> >
> > The principle looks like this:
> >
> >
> > *try {*
> >
> > *    withMaven()*
> >
> > *} finally {*
> >
> > *    cleanWs()*
> > *}*
> >
> > This is the stacktrace:
> >
> > [windows] [INFO] BUILD SUCCESS
> > [windows] [INFO]
> > ------------------------------------------------------------------------
> > [windows] [INFO] Total time: 43:08 min
> > [windows] [INFO] Finished at: 2018-02-18T04:34:10+00:00
> > [windows] [INFO] Final Memory: 48M/161M
> > [windows] [INFO]
> > ------------------------------------------------------------------------
> > [windows] [INFO] [jenkins-event-spy] Generated
> >
> > F:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-
> VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp
> > \withMavene898fc1f\maven-spy-20180218-035101-1877982869374894449694.log
> > [windows] Picked up JAVA_TOOL_OPTIONS:
> >
> > -Dmaven.ext.class.path="f:\jenkins\jenkins-slave\workspace\n-wip_maven-
> surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp
> > \withMavene898fc1f\pipeline-maven-spy.jar"
> >
> > -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="
> f:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-
> VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp
> > \withMavene898fc1f"
> >
> > [Pipeline] [windows] }
> > [windows] ERROR: [withMaven] WARNING Exception processing the logs
> > generated by the Jenkins Maven Event Spy
> >
> > f:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-
> VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp
> > \withMavene898fc1f\maven-spy-20180218-042026-3958838718902276550716.log,
> > ignore file.  Please report a bug associated for the component
> > 'pipeline-maven-plugin' at https://issues.jenkins-ci.org
> > [windows] java.lang.InterruptedException
> > [windows]     at java.lang.Object.wait(Native Method)
> > [windows]     at hudson.remoting.Request.call(Request.java:167)
> > [windows]     at hudson.remoting.Channel.call(Channel.java:907)
> > [windows]     at hudson.FilePath.act(FilePath.java:986)
> > [windows]     at hudson.FilePath.act(FilePath.java:975)
> > [windows]     at hudson.FilePath.exists(FilePath.java:1440)
> > [windows]     at
> >
> > org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.
> processMavenSpyLogs(MavenSpyLogProcessor.java:105)
> > [windows]     at
> >
> > org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$
> WorkspaceCleanupCallback.finished(WithMavenStepExecution.java:1015)
> > [windows]     at
> >
> > org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$
> TailCall.onSuccess(BodyExecutionCallback.java:114)
> > [windows]     at
> >
> > org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$
> SuccessAdapter.receive(CpsBodyExecution.java:368)
> > [windows]     at
> > com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73)
> > [windows]     at
> > com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:166)
> > [windows]     at
> > com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
> > [windows]     at
> >
> > org.codehaus.groovy.runtime.GroovyCategorySupport$
> ThreadCategoryInfo.use(GroovyCategorySupport.java:122)
> > [windows]     at
> >
> > org.codehaus.groovy.runtime.GroovyCategorySupport.use(
> GroovyCategorySupport.java:261)
> > [windows]     at
> > com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
> > [windows]     at
> >
> > org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(
> SandboxContinuable.java:19)
> > [windows]     at
> >
> > org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(
> SandboxContinuable.java:35)
> > [windows]     at
> >
> > org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(
> SandboxContinuable.java:32)
> > [windows]     at
> >
> > org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.
> GroovySandbox.runInSandbox(GroovySandbox.java:108)
> > [windows]     at
> >
> > org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(
> SandboxContinuable.java:32)
> > [windows]     at
> >
> > org.jenkinsci.plugins.workflow.cps.CpsThread.
> runNextChunk(CpsThread.java:174)
> > [windows]     at
> >
> > org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.
> run(CpsThreadGroup.java:331)
> > [windows]     at
> >
> > org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.
> access$200(CpsThreadGroup.java:82)
> > [windows]     at
> >
> > org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.
> call(CpsThreadGroup.java:243)
> > [windows]     at
> >
> > org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.
> call(CpsThreadGroup.java:231)
> > [windows]     at
> >
> > org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(
> CpsVmExecutorService.java:64)
> > [windows]     at java.util.concurrent.FutureTask.run(FutureTask.
> java:266)
> > [windows]     at
> >
> > hudson.remoting.SingleLaneExecutorService$1.
> run(SingleLaneExecutorService.java:112)
> > [windows]     at
> >
> > jenkins.util.ContextResettingExecutorService$1.run(
> ContextResettingExecutorService.java:28)
> > [windows]     at
> > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> > [windows]     at java.util.concurrent.FutureTask.run(FutureTask.
> java:266)
> > [windows]     at
> >
> > java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1149)
> > [windows]     at
> >
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:624)
> > [windows]     at java.lang.Thread.run(Thread.java:748)
> >
> --
> Sent from my phone
>