Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-35351

Rerun the running job to other availalbe slaves if connection channel lost in current slave

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Critical Critical
    • core
    • None
    • Ubuntu 14.04 server 64bit
      Jenkins 1.651.1
      oracle-java7 1.7.0_80

      Sometimes during the build,
      we randomly run into issues of:
      java.io.IOException: Unexpected termination of the channel
      or
      hudson.remoting.ChannelClosedException: channel is already closed
      or
      java.io.EOFException

      where Jenkins master lost the connection channel
      to the Jenkins slaves which are running the build job.
      When this happened, the build job is failed.
      This is inconvenient for long-build nightly jobs.

      Instead of failing the job,
      the Jenkins master to re-dispatch the same job (same build number / parameters / configurations) to the next available Jenkins slaves,
      and re-start over.

            Unassigned Unassigned
            totoroliu Rick Liu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: