-
New Feature
-
Resolution: Fixed
-
Minor
While working on the design for JENKINS-51413, I and pvtuan10 noticed that SlaveComputer#setChannel() interface allows creating channels only based on I/O streams albeit the Channel logic itself and ChannelBuilders support other command transports.
I propose to add a new API methods so that other channel implementations can be defined by ComputerLaunchers (see Option 2 in JENKINS-51413)
- relates to
-
JENKINS-51413 Implementation of producer-consumer basic communication
-
- Resolved
-
-
JENKINS-51551 Allow CommandTransport and its sub-classes to be sub-typed from outside
-
- Resolved
-
Code changed in jenkins
User: Oleg Nenashev
Path:
core/src/main/java/hudson/slaves/SlaveComputer.java
pom.xml
http://jenkins-ci.org/commit/jenkins/c405ae701c4bca18f7b4edc6e5cd3bc053b7ee60
Log:
[JENKINS-51541,JENKINS-51551,...] - Remoting 3.21 + Allow passing custom CommandTransport implementations to SlaveComputer from ComputerLauncher (#3455)
JENKINS-51541- Introduce new SlaveComputer#setChannel() method which takes custom ChannelBuilder and CommandTransportJENKINS-51551- Pick Remoting version with the API patchJENKINS-51541- Listener is nullable according to the documentationJENKINS-51541- Restrict SlaveComputer#setChannel(ChannelBuilder cb, …) to Beta-use only*NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/
Functionality will be removed from GitHub.com on January 31st, 2019.