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 "Using Hudson/Using Hudson plugins"
(New page: This article is a stub. It will be expanded as content is migrated from the [http://wiki.hudson-ci.org/display/HUDSON/Use+Hudson|Use Hudson-CI]Web site.) |
|||
| Line 1: | Line 1: | ||
This article is a stub. It will be expanded as content is migrated from the [http://wiki.hudson-ci.org/display/HUDSON/Use+Hudson|Use Hudson-CI]Web site. | This article is a stub. It will be expanded as content is migrated from the [http://wiki.hudson-ci.org/display/HUDSON/Use+Hudson|Use Hudson-CI]Web site. | ||
| + | |||
| + | Hudson is extended through the use of plugins. Plugins integrate Hudson with a range of build, SCM, testing and other ALM/SDLC tools | ||
| + | |||
| + | Plugins are categorized into three levels: | ||
| + | Tier 1 or core plugins are defined as being part of the Hudson Core, for the purposes of committer rights | ||
| + | Tier 2 plugins are a growing group of plugins that are tested as part of the QA certification process of each release (from release 1.398) | ||
| + | Tier 3 are those plugins that do not yet have functional testing done as part of the release process. | ||
| + | Other plugins with no tier details have not yet been assessed into a tier. the assessed plugins represent the most popular plugins. If you would like a specific plugin to be assessed into a tier please mail the dev list | ||
| + | |||
| + | How to install a plugin | ||
| + | How to develop your own plugin | ||
| + | How to release your plugin | ||
| + | How to host your plugin | ||
| + | Plugins By Topic Overview | ||
| + | Hudson Community Internal Plugins | ||
| + | Hudson Community External Plugins | ||
| + | |||
| + | {anchor:tier1} | ||
| + | Tier 1 (core) Plugins | ||
| + | |||
| + | The following plugins are defined as being part of the Hudson Core, for the purposes of committer rights: | ||
| + | |||
| + | CVS Plugin | ||
| + | Maven 2 Project Plugin | ||
| + | Maven 3 Plugin | ||
| + | SSH Slaves plugin | ||
| + | Subversion Plugin | ||
| + | Git Plugin (From release 2.1.0) | ||
| + | |||
| + | Tier 1 plugins are shipped with the Hudson core. They are tested as part of the QA certification process | ||
| + | {anchor:tier2} | ||
| + | Tier 2 Plugins | ||
| + | |||
| + | The following plugins are Hudson maintainedand in addition are tested as part of the QA certification process | ||
| + | |||
| + | disk usage | ||
| + | copy-artifact | ||
| + | parameterized trigger | ||
| + | promoted builds | ||
| + | deploy | ||
| + | build timeout | ||
| + | join | ||
| + | |||
| + | {anchor:tier3} | ||
| + | Tier 3 Plugins | ||
| + | |||
| + | These plugins fall into 4 categories: | ||
| + | |||
| + | Hudson - plugins developed and maintained for the Hudson community | ||
| + | Compatible - tested by their owners for compatibility between Hudson and Jenkins | ||
| + | Install Tested - those that, on release of a new plugin version, are tested by the Hudson community that they at least install correctly. But there is no stated compatibility from Jenkins | ||
| + | Other - plugins that have not been identified as belonging to any of the above categories | ||
| + | |||
| + | How to install plugins | ||
| + | {anchor:install} | ||
| + | Using the interface | ||
| + | |||
| + | The simplest way is by going to your installation's management screen and clicking Manage Plugins (http://yourhost/hudson/pluginManager/). The web interface will then download *.hpi files from here, and you will just need to restart your Hudson to pick up the changes. | ||
| + | By hand | ||
| + | |||
| + | Download Site | ||
| + | |||
| + | Save the downloaded *.hpi file into the $HUDSON_HOME/plugins directory. You will then need to restart Hudson (many containers let you do this without restarting the container.) | ||
| + | |||
| + | Caveat: the names of the plugin directories on the download site are not always matching the name given to the plugin; common sense should apply. | ||
| + | Developer Information | ||
| + | |||
| + | Plugin developers should take a look at Hosting Hudson Plugins | ||
| + | |||
| + | Hosting Hudson Plugins | ||
| + | report of unreleased plugin changes | ||
| + | Source code copyright | ||
Revision as of 21:50, 3 December 2012
This article is a stub. It will be expanded as content is migrated from the Hudson-CIWeb site.
Hudson is extended through the use of plugins. Plugins integrate Hudson with a range of build, SCM, testing and other ALM/SDLC tools
Plugins are categorized into three levels:
Tier 1 or core plugins are defined as being part of the Hudson Core, for the purposes of committer rights
Tier 2 plugins are a growing group of plugins that are tested as part of the QA certification process of each release (from release 1.398)
Tier 3 are those plugins that do not yet have functional testing done as part of the release process.
Other plugins with no tier details have not yet been assessed into a tier. the assessed plugins represent the most popular plugins. If you would like a specific plugin to be assessed into a tier please mail the dev list
How to install a plugin How to develop your own plugin How to release your plugin How to host your plugin Plugins By Topic Overview Hudson Community Internal Plugins Hudson Community External Plugins
{anchor:tier1} Tier 1 (core) Plugins
The following plugins are defined as being part of the Hudson Core, for the purposes of committer rights:
CVS Plugin Maven 2 Project Plugin Maven 3 Plugin SSH Slaves plugin Subversion Plugin Git Plugin (From release 2.1.0)
Tier 1 plugins are shipped with the Hudson core. They are tested as part of the QA certification process {anchor:tier2} Tier 2 Plugins
The following plugins are Hudson maintainedand in addition are tested as part of the QA certification process
disk usage copy-artifact parameterized trigger promoted builds deploy build timeout join
{anchor:tier3} Tier 3 Plugins
These plugins fall into 4 categories:
Hudson - plugins developed and maintained for the Hudson community Compatible - tested by their owners for compatibility between Hudson and Jenkins Install Tested - those that, on release of a new plugin version, are tested by the Hudson community that they at least install correctly. But there is no stated compatibility from Jenkins Other - plugins that have not been identified as belonging to any of the above categories
How to install plugins {anchor:install} Using the interface
The simplest way is by going to your installation's management screen and clicking Manage Plugins (http://yourhost/hudson/pluginManager/). The web interface will then download *.hpi files from here, and you will just need to restart your Hudson to pick up the changes. By hand
Download Site
Save the downloaded *.hpi file into the $HUDSON_HOME/plugins directory. You will then need to restart Hudson (many containers let you do this without restarting the container.)
Caveat: the names of the plugin directories on the download site are not always matching the name given to the plugin; common sense should apply. Developer Information
Plugin developers should take a look at Hosting Hudson Plugins
Hosting Hudson Plugins report of unreleased plugin changes Source code copyright