Jenkins' i18n support has some aspects that developers need to be aware of. Generation of type-safe Messages classes from Messages.properties. Marking messages ...

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

This allows you to read the Jenkins core source code as you develop plugins. (Or just select Download Sources on the Dependencies node.) You are advised to ...

Extensions Index. Jenkins defines extension points, which are interfaces or abstract classes that model an aspect of its behavior. Those interfaces define ...

Your plugin source code will be hosted in a repository in the jenkinsci GitHub organization. You will have admin access to this repository.

In Jenkins, you need add a similar .properties file with the .groovy file in the same directory. Any changes of .properties does not need restart Jenkins or ...

Writing Pipeline-Compatible Plugins. Plugin Developer Guide. If you are maintaining (or creating) a plugin and wish its features to work smoothly with Pipeline, ...

The source code for your test cases should be placed in the standard location for Maven projects, i.e. under the src/test/java/ directory. Examples. To see some ...

Copy that URL in your web browser and submit a pull request. A job will be automatically created in the ci.jenkins.io Plugins folder after the pull request is ...

Plugin documentation is migrating to GitHub. Instructions are available on the www.jenkins.io site. Create a branch. In a local copy of your fork of the ...