-
New Feature
-
Resolution: Duplicate
-
Major
-
None
-
Jenkins ver. 2.53
Pipeline job /
Pipeline: Nodes and Processes plugins : ver. 2.10
Preconditions
Jenkins pipeline job is configured to run parallel actions in different docker swarm nodes.
Procedure
- Run job
- Force disconnect of a node running a part of this job
Actual outcome
Job will never terminate. The pipeline part will remain stuck in:
Cannot contact swarm-xxxxxxxx: hudson.remoting.RequestAbortedException: java.nio.channels.ClosedChannelException
The exception is catched by workflow-durable-task-step-plugin and used to display the log above.
Expected outcome
The pipeline part execution should generate an exception that can be catched.
This will can allow implementing a retry strategy in Pipeline job.
- duplicates
-
JENKINS-49707 Auto retry for elastic agents after channel closure
-
- Resolved
-
- relates to
-
JENKINS-36013 Automatically abort ExecutorPickle rehydration from an ephemeral node
-
- Closed
-
As with
JENKINS-36013, currently the model is that a node may go offline and later be reconnected, in which case the step will quietly resume printing output and exit normally. For Swarm or other cloud-like node schemes, a disconnection may be followed by an actual permanent removal of the node definition, in which case it would be desirable for the step to abort.