[JIRA] (JENKINS-59507) if agent is temporarily offline build will fail.

5 views
Skip to first unread message

jnord@cloudbees.com (JIRA)

unread,
Sep 24, 2019, 7:30:04 AM9/24/19
to jenkinsc...@googlegroups.com
James Nord created an issue
 
Jenkins / Bug JENKINS-59507
if agent is temporarily offline build will fail.
Issue Type: Bug Bug
Assignee: Alvaro Lobato
Components: pipeline-maven-plugin
Created: 2019-09-24 11:29
Priority: Minor Minor
Reporter: James Nord

pipelines are supposed to be tollerant to Jenkins / agent disconnections.

 

However I noted one of our pipelines failed due to withMaven step (in the record) performing an action when it was not connected.  (I beleive due to a Jenkins restart).

 

last logs from withMaven are

 

[2019-09-24T06:43:57.513Z] [INFO] BUILD SUCCESS
[2019-09-24T06:43:57.513Z] [INFO] ------------------------------------------------------------------------
[2019-09-24T06:43:57.513Z] [INFO] Total time:  13:10 min
[2019-09-24T06:43:57.513Z] [INFO] Finished at: 2019-09-24T06:43:56Z
[2019-09-24T06:43:57.513Z] [INFO] ------------------------------------------------------------------------
[2019-09-24T06:43:57.513Z] [INFO] [jenkins-event-spy] Generated C:\e4909a8e\workspace\_jobname-140@tmp\withMaven87aef991\maven-spy-20190924-063045-3358730318194673428250.log
[2019-09-24T06:43:57.513Z] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="C:\e4909a8e\workspace\jobname-140-140@tmp\withMaven87aef991\pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="C:\e4909a8e\workspace\jobname-140-140@tmp\withMaven87aef991" 
[Pipeline] }
[Pipeline] // withMaven 

 

normally this will continue on with findbugs/spotbugs analysis

 

java.nio.channels.ClosedChannelException
	at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
	at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142)
	at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
	at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
	at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from xxx/1.1.1.1:33798 failed. The channel is closing down or has closed down
	at hudson.remoting.Channel.call(Channel.java:950)
	at hudson.FilePath.act(FilePath.java:1070)
	at hudson.FilePath.act(FilePath.java:1059)
	at hudson.FilePath.list(FilePath.java:1893)
	at hudson.FilePath.list(FilePath.java:1877)
	at hudson.FilePath.list(FilePath.java:1862)
	at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:71)
	at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution2$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution2.java:1108)
	at org.jenkinsci.plugins.pipeline.maven.fix.jenkins49337.GeneralNonBlockingStepExecution$TailCall.lambda$onSuccess$0(GeneralNonBlockingStepExecution.java:142)
	at org.jenkinsci.plugins.pipeline.maven.fix.jenkins49337.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:85)
	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)
Finished: FAILURE 

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

jnord@cloudbees.com (JIRA)

unread,
Sep 24, 2019, 7:35:02 AM9/24/19
to jenkinsc...@googlegroups.com
James Nord updated an issue
Change By: James Nord
pipeline-maven-plugin  3.7.1, Jenkins 2.176

pipelines are supposed to be tollerant to Jenkins / agent disconnections.

 

However I noted one of our pipelines failed due to {{withMaven}} step (in the record) performing an action when it was not connected.  (I beleive due to a Jenkins restart).

 

last logs from withMaven are

 
{noformat}

[2019-09-24T06:43:57.513Z] [INFO] BUILD SUCCESS
[2019-09-24T06:43:57.513Z] [INFO] ------------------------------------------------------------------------
[2019-09-24T06:43:57.513Z] [INFO] Total time:  13:10 min
[2019-09-24T06:43:57.513Z] [INFO] Finished at: 2019-09-24T06:43:56Z
[2019-09-24T06:43:57.513Z] [INFO] ------------------------------------------------------------------------
[2019-09-24T06:43:57.513Z] [INFO] [jenkins-event-spy] Generated C:\e4909a8e\workspace\_jobname-140@tmp\withMaven87aef991\maven-spy-20190924-063045-3358730318194673428250.log
[2019-09-24T06:43:57.513Z] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="C:\e4909a8e\workspace\jobname-140-140@tmp\withMaven87aef991\pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="C:\e4909a8e\workspace\jobname-140-140@tmp\withMaven87aef991"
[Pipeline] }
[Pipeline] // withMaven {noformat}

 

normally this will continue on with findbugs/spotbugs analysis

 
{noformat}

java.nio.channels.ClosedChannelException
at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142)
at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from xxx/1.1.1.1:33798 failed. The channel is closing down or has closed down
at hudson.remoting.Channel.call(Channel.java:950)
at hudson.FilePath.act(FilePath.java:1070)
at hudson.FilePath.act(FilePath.java:1059)
at hudson.FilePath.list(FilePath.java:1893)
at hudson.FilePath.list(FilePath.java:1877)
at hudson.FilePath.list(FilePath.java:1862)
at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:71)
at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution2$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution2.java:1108)
at org.jenkinsci.plugins.pipeline.maven.fix.jenkins49337.GeneralNonBlockingStepExecution$TailCall.lambda$onSuccess$0(GeneralNonBlockingStepExecution.java:142)
at org.jenkinsci.plugins.pipeline.maven.fix.jenkins49337.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:85)
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)
Finished: FAILURE {noformat}
 
Reply all
Reply to author
Forward
0 new messages