Jenkins pipeline not aborted when the machine running docker container goes offline

XMLWordPrintable

    • Type: New Feature
    • Resolution: Duplicate
    • Priority: Major
    • None
    • Environment:
      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

      1. Run job
      2. 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.

            Assignee:
            Unassigned
            Reporter:
            Aymen Bouaziz
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: