-
New Feature
-
Resolution: Unresolved
-
Major
Currently Remoting protocols have handlers hardcoded in the core, and any update (e.g. new protocol or a patch) requires inclusion into the Jenkins core. I propose to create a new plugin, which would store such protocol logic and maybe other Remoting boilerplate stuff.
- is related to
-
JENKINS-26463 Split CLI out of core
-
- Open
-
-
JENKINS-26465 Split JNLP slaves from core
-
- Open
-
- relates to
-
JENKINS-50211 Reject connections from agents with unsupported Remoting versions
-
- Closed
-
-
JENKINS-55582 Convert modules to plugins
-
- Resolved
-
- links to
(1 links to)
[JENKINS-44100] Detach Remoting protocol management logic in Jenkins core to a plugin
Epic Link | New: JENKINS-44099 [ 181725 ] |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Summary | Original: Detach Remoting protocol management logic to a plugin | New: Detach Remoting protocol management logic in Jenkins core to a plugin |
Link | New: This issue is related to JENKINS-26465 [ JENKINS-26465 ] |
Link | New: This issue is related to JENKINS-26463 [ JENKINS-26463 ] |
Issue Type | Original: New Feature [ 2 ] | New: Epic [ 10001 ] |
Epic Link | Original: JENKINS-44099 [ 181725 ] |
Epic Name | New: Remoting - Detach Remoting CLI and Agent support to a plugin |