Shulou(Shulou.com)06/02 Report--

This article shows you the Alpha version of the plug-in management library and what is the CLI tool, the content is concise and easy to understand, can definitely brighten your eyes, through the detailed introduction of this article, I hope you can get something.

Alpha version of the plug-in management library and CLI tools

Alpha version of the plug-in management library and CLI tools

"everyone is repeating the wheel, some of which are like the" details "of implementing plug-in management (signature metadata, product checksum, plug-ins independent from the core …). It is clear that Jenkins should provide sufficient tools for plug-in installation outside of real-time Jenkins instances." JENKINS-53767

My Google Summer of Code project project tries to solve this problem by creating a library that unifies plug-in management logic in different implementations of Jenkins and provides a CLI tool that makes it easy for users to download plug-ins and view plug-in information before Jenkins starts. I am very happy to share the Alpha version we just released, you can check it here!

GSoC Phase 1 update

When I considered moving the plug-in manager out of the Jenkins core, this turned out to be the most challenging first step because of the complexity and number of dependencies. Instead, we decided to first convert the install-plugins.sh bash script in Jenkins Docker to Java. The install-plugins.sh script has several problems, that is, it is an bash script with limited extensibility, and it does not retrieve metadata from all the latest update centers.

Alpha version details

Mimicking the actions in the install-plugins.sh script in the official Jenkins Docker image, the new plug-in management library receives a list of plug-ins, their versions, and / or URL, from which you can download plug-ins and download the required plug-ins and their dependencies. The plug-in is downloaded from the update center to the specified directory and can then be loaded into Jenkins. Currently, the plug-ins to be downloaded can be specified through the plugins.txt file and / or the cli option of-plugins, and we plan to further expand the input formats that can be received. Custom version specifiers for different update centers are also supported.

The library will first check whether any requested plug-ins are currently installed in the user-specified download location or in the user-specified Jenkins war file. If a later version or later is required as a dependency, installed plug-ins are ignored or upgraded. After determining that the plug-in downloads URL, the library downloads the plug-in and parses and downloads its dependencies.

This is just the beginning: the plug-in manager library and cli tools are still under development. More powerful input parsing, support for security warnings and available updates, Docker integration, and other features are coming soon!

The above is the Alpha version of the plug-in management library and what are the CLI tools? have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.