-
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
[JENKINS-55582] Convert modules to plugins
Assignee | New: Jesse Glick [ jglick ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Description |
Original:
None of the [currently bundled {{jenkins-module}} packages|https://github.com/jenkinsci/jenkins/blob/6d2eb679a6fccc53d32708cc23c5927201953248/war/pom.xml#L95-L134] 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|https://javadoc.jenkins.io/jenkins/security/ConfidentialStore.html]. 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, in the case of {{sshd}} / {{git-server}} this would allow the older and deprecated half of {{workflow-cps-global-lib}} to be split into its own plugin so that the {{org.jenkinsci.plugins.workflow.libs}} package can be used without reference to existing modules. This would lighten its footprint and simplify some functional test configuration. |
New:
None of the [currently bundled {{jenkins-module}} packages|https://github.com/jenkinsci/jenkins/blob/6d2eb679a6fccc53d32708cc23c5927201953248/war/pom.xml#L95-L134] 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|https://javadoc.jenkins.io/jenkins/security/ConfidentialStore.html]. 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 |
Link | New: This issue relates to JENKINS-44100 [ JENKINS-44100 ] |
Link |
New:
This issue relates to |
Remote Link | New: This issue links to "instance-identity #17 (Web Link)" [ 22602 ] |
Started off by making sure they all at least have up-to-date build metadata, which should make things easier.