Package a Library Source as a Plugin¶
Users can package their Library Source as a stand-alone Jenkins Plugin.
This has a couple advantages:
- Performance: Avoid fetching from a remote repository on every Pipeline Run
- Plugin Dependencies: Ensure the Jenkins Plugins your libraries depend upon are installed
Gradle JTE Plugin¶
To package your Library Source, the simplest path is to use the Gradle JTE Plugin.
plugins{
// used to packate these libraries as a jenkins plugin
id "io.jenkins.jte" version "0.2.0"
}
You can use the configuraiton options defined in the README to configure the plugin.
To package your Library Source, run ./gradlew jte
.
The hpi
file will be output to your projects build directory.
from there, you can install the hpi
file via the Jenkins UI.
Note
To see an example Library Source, check out the jte-library-scaffold.