How code is physically structured in Jenkins core and plugins, and how this relates to dependencies and Java class loading behavior. Optional dependencies

Sep 7, 2021 · A plugin needs to have an .hpi extension. The file name body ("foo" portion) of the file name is used as the "short name" of a plugin, ...

This tutorial serves as a starting point for Jenkins plugin development: It explains how to prepare your build environment, how to create a plugin, and how to ...

Maven has created the project structure in a directory with the same name as you chose for your plugin. We will rename the directory to match the conventional ...

... Plugin Structure: pom.xml. Maven uses the pom.xml file to build your Jenkins plugin. All Jenkins plugins should be based on the Plugin Parent POM: <parent> ...

Documentation is an important part of any Jenkins plugin. It includes user documentation (plugin pages, changelogs, user guidelines, etc.) ...

Plugin Development · Plugin Governance · Publishing Plugins · Style Guides · Source Code Hosting · Artifact Repository · Plugin Documentation · Plugin Wiki ...

Creating a new plugin. Please read this guide before you start if you intend to release your plugin publicly using the Jenkins project infrastructure.

The SCM plugin architecture section covers how to create the base classes and jelly files that a SCM implementation requires. The Remoting section covers how ...

Jenkins is based on Java, so to build Jenkins plugins you need to install a Java Development Kit (JDK). Java 17 is the version we recommend to users, ...