[JIRA] (JENKINS-60762) pipeline used to wait to schedule task now stops immediately
Title: Message Title Roman Pickl updated JENKINS-60762 we cannot reproduce this after some updates. Jenkins / JENKINS-60762 pipeline used to wait to schedule task now stops immediately Change By: Roman Pickl Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion
[JIRA] (JENKINS-60762) pipeline used to wait to schedule task now stops immediately
Title: Message Title Roman Pickl updated JENKINS-60762 Jenkins / JENKINS-60762 pipeline used to wait to schedule task now stops immediately Change By: Roman Pickl Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204023.1579003891000.19019.1588091460278%40Atlassian.JIRA.
[JIRA] (JENKINS-60762) pipeline used to wait to schedule task now stops immediately
Title: Message Title
Roman Pickl updated an issue
Jenkins / JENKINS-60762
pipeline used to wait to schedule task now stops immediately
Change By:
Roman Pickl
I'm not sure this is a bug, but I want to file it anyway:We have a declarative pipeline where we need to restart one of the nodes and continue in a later stage.So in this node we do {noformat} bat 'shutdown /s /t 30 & exit 0' {noformat} The next step uses the same node.Before updating some plugins and or jenkins (I assume the jenkins plugins) it behaved like this: When trying to run the following stage on this node, the node is not connected yet, jenkins is{noformat}Still waiting to schedule task'' is offline{noformat}and then after it started and connected it schedules the task and finishes the stage successfully.after the update it immediately fails with:{noformat} was marked offline: Connection was broken: java.nio.channels.ClosedChannelExceptionat org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179)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)at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)at java.lang.Thread.run(Unknown Source){noformat} I solved this with adding a sleep to wait for the machine to be online again, but is there a better solution?
Add Comment
[JIRA] (JENKINS-60762) pipeline used to wait to schedule task now stops immediately
Title: Message Title Roman Pickl created an issue Jenkins / JENKINS-60762 pipeline used to wait to schedule task now stops immediately Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2020-01-14 12:11 Environment: Jenkins ver. 2.204.1 Priority: Minor Reporter: Roman Pickl I'm not sure this is a bug, but I want to file it anyway: We have a declarative pipeline where we need to restart one of the nodes and continue in a later stage. So in this node we do bat 'shutdown /s /t 30 & exit 0' The next step uses the same node. Before updating some plugins and or jenkins (I assume the jenkins plugins) it behaved like this: When trying to run the following stage on this node, the node is not connected yet, jenkins is Still waiting to schedule task '' is offline and then after it started and connected it schedules the task and finishes the stage successfully. after the update it immediately fails with: was marked offline: Connection was broken: java.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179) at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795) at
