How to view Jenkins in your language. Translations to Specific languages. What developers need to know/do. Generation of Messages classes; Marking messages in ...
Missing: /url | Show results with:/url
Documentation is an important part of any Jenkins plugin. It includes user documentation (plugin pages, changelogs, user guidelines, etc.) ...
Properties files should be UTF-8 encoded, at least for core or plugins which already use Java 11 or newer and a core version greater than 2.358.
Missing: /url | Show results with:/url
Install Apache Maven. Jenkins plugins are built with Apache Maven. Download Maven from the Apache Maven website. Make sure to download one of the ...
Extensions Index. Jenkins defines extension points, which are interfaces or abstract classes that model an aspect of its behavior. Those interfaces define ...
Missing: /url | Show results with:/url
The Jenkins project hosts a Jenkins instance to perform continuous integration builds for plugins. We recommend you set up CI builds for your plugin in the ...
Additionally for modern web UIs, localized resources are exposed at /i18n/resourceBundle/ , at URLs like https://ci.jenkins.io/i18n/resourceBundle?baseName= ...
Writing Pipeline-Compatible Plugins. Plugin Developer Guide. If you are maintaining (or creating) a plugin and wish its features to work smoothly with Pipeline, ...
Missing: /url | Show results with:/url
Permission, which represents an activity that requires a security privilege. This is usually a verb, like "configure", "administer", "tag", etc.
Be sure to provide the following information: Link to a plugin you want to adopt. The status of the plugin ("for adoption" or "abandoned").
Missing: /url | Show results with:/url