Hi all, I am working on optimizing plugin bundling in Jenkinsfile Runner (issue 389 <https://github.com/jenkinsci/jenkinsfile-runner/issues/389>, 390 <https://github.com/jenkinsci/jenkinsfile-runner/issues/390>). Jenkinsfile Runner supports a performance-optimized mode when Jenkins core and its plugins are packaged as JAR files using Maven Assembly Plugin. Unfortunately Jenkins still needs an exploded HPI file to read the plugin manifests.
To resolve this, I would need to apply patches in Jenkinsfile Runner plugin manager and in Maven HPI Plugin which currently generates the list of dependencies included into Jenkinsfile Runner. Later I will also need to modify the Plugin Installation Manager Tool so that it can also recognize this form of plugin bundling. So it needs an interexchange format and a shared library so that tools do not need to reimplement the model and IO logic. We already have Jenkins JEP-309: Bill of Materials <https://github.com/jenkinsci/jep/blob/master/jep/309> which defines a YAML file format for exchanging data between Jenkins tools. A few years ago I added support for YAML BOM in Custom WAR Packager <https://github.com/jenkinsci/custom-war-packager>. I would like to use this format (not ideal, but works), and I started detaching the model from CWP to a library. - Library draft: https://github.com/oleg-nenashev/lib-bom-jep309 - Hosting request: https://issues.jenkins.io/browse/HOSTING-1050 Would appreciate feedback from other contributors who might be interested to use JEP-309 BOMs in their tools Thanks in advance, Oleg -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b3b97369-4609-4272-b4e0-a1fe6351821an%40googlegroups.com.
