-
New Feature
-
Resolution: Fixed
-
Major
-
None
- Add an option to start a slave.jar with JNLP connection and then terminate the spawning SSH. This allows to use NIO-based Channels with EC2 plugin and reduce the number of threads maintained with SSH-based communication links.
- Would allow a slave process to reconnect to master.
- depends on
-
JENKINS-25209 Add "reboot slave after build" for a slave template
-
- Open
-
- is related to
-
JENKINS-25672 Distributed deadlock with remote classloading
-
- Open
-
-
JENKINS-25697 Channel A with ProxyInput/OutputStream to another Channel B will hang and leak if Channel B is terminated
-
- Open
-
[JENKINS-25626] Allow an option to start a JNLP agent and terminate SSH connection
Link | New: This issue depends on JENKINS-25209 [ JENKINS-25209 ] |
Description | Original: # Add an option to start a slave.jar with JNLP connection and then terminate the spawning SSH. This allows to use NIO-based Channels with EC2 plugin and reduce the number of threads maintained with SSH-based communication links. |
New:
# Add an option to start a slave.jar with JNLP connection and then terminate the spawning SSH. This allows to use NIO-based Channels with EC2 plugin and reduce the number of threads maintained with SSH-based communication links. # Would allow a slave process to reconnect to master. |
Link | New: This issue is related to JENKINS-25697 [ JENKINS-25697 ] |
Link | New: This issue is related to JENKINS-25672 [ JENKINS-25672 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Workflow | Original: JNJira [ 159600 ] | New: JNJira + In-Review [ 208231 ] |