Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Hudson-ci/Extend Hudson"
(→Additional references) |
(→Additional references) |
||
| Line 47: | Line 47: | ||
== Additional references == | == Additional references == | ||
| − | *[ | + | *[http://hudson-ci.org/javadoc/ Hudson Javadoc] |
*Jelly taglib reference [http://commons.apache.org/proper/commons-jelly/tags.html core] [http://commons.apache.org/proper/commons-jelly/libs/define/tags.html define] | *Jelly taglib reference [http://commons.apache.org/proper/commons-jelly/tags.html core] [http://commons.apache.org/proper/commons-jelly/libs/define/tags.html define] | ||
Revision as of 20:11, 23 July 2013
This page is a stub, and in progress.
Developing Plugins
Hudson supports plugins, which allow Hudson to be extended to meet specific needs of individual projects. Read on to learn how to write a plugin.
- Write your first Hudson Plugin
- Plugin Architecture
- Plugin Directory Structure
- Sample - Writing an SCM plugin
- Extension points
- Dependencies among plugins
- Writing Plugin code
- Using IntelliJ IDEA plugin
- Structured Form Submission
- Making your plugin behave in distributed Hudson
- Making your plugin behave in secured Hudson
- Marking a new plugin version as incompatible with older versions
- Hints for plugin-development newbies
- Exposing data to the remote API
- Writing CLI commands
- Participating to the initialization
- Writing Plugin UI using Jelly Framework
- Writing unit tests for your plugin
- Writing UI integration tests for your plugin
- Understanding Stapler URL mapping rules
- Tips
Additional references
- Hudson Javadoc
- Jelly taglib reference core define