-
Task
-
Resolution: Fixed
-
Major
-
-
2.357
None of the currently bundled jenkins-module packages actually look like they need to be modules: they do not appear to need to be loaded in the same class loader as jenkins-core.jar, nor to have extensions/services registered early in the startup sequence. As such, they could be made into regular plugins (hpi packaging), and the usual split-plugins.txt registry used to retain compatibility for existing plugins which happen to refer to their classes (InstanceIdentity and SshCommandFactory are the main examples).
As an aside refiled as JENKINS-57023.
- causes
-
JENKINS-70206 jenkins.security.Security218Test#jnlpSlave is flaky
- Closed
-
JENKINS-64107 Convert SSHD module to a plugin
- Closed
- is blocked by
-
JENKINS-57071 Cannot use Linux agent installer modules
- Resolved
-
JENKINS-57023 Split external library functionality into its own plugin
- Closed
- is blocking
-
JENKINS-64104 Upgrade and migrate to Apache Mina SSH 2.x
- In Progress
-
JENKINS-68662 Instance identity plugin can't encode/decode PEM in a FIPS configured OS / host
- Closed
- is related to
-
JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data
- Resolved
- relates to
-
JENKINS-41987 Cryptic error message when loading JnlpSlaveAgentProtocol4
- Resolved
-
JENKINS-44100 Detach Remoting protocol management logic in Jenkins core to a plugin
- Open
- links to