Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Hudson-ci/Extend Hudson"
| Line 22: | Line 22: | ||
**[[Writing CLI commands]] | **[[Writing CLI commands]] | ||
**[[Participating to the initialization]] | **[[Participating to the initialization]] | ||
| − | *Writing Plugin UI using Jelly Framework | + | *Writing Plugin UI using Jelly Framework |
**[[Basic guide to Jelly usage in Hudson]] | **[[Basic guide to Jelly usage in Hudson]] | ||
**[[Understanding Jelly Tags]] | **[[Understanding Jelly Tags]] | ||
Revision as of 14:48, 17 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