Hudson is extended through the use of plugins. Plugins integrate Hudson with a range of build, SCM, testing and other ALM/SDLC tools.

All available plugins can be browsed at Hudson Plugin Central

• Plugin Categories
• Plugins By Topic Overview
• How to install a plugin
• How to develop your own plugin
• How to release your plugin
• How to host your plugin

Plugin Categories

Compatibility or Mandatory Plugins

Following plugins are mandatory for Hudson (3.0.0 and newer) to work properly. They must be installed before using Hudson.

• Native Access Plugin
• BIRT Charts plugin
• Xpath support plugin

Featured Plugin

The following plugins are developed and maintained by Hudson core team. They are tested as part of the QA certification process

• CVS Plugin
• JFreechart plugin
• Git Plugin
• Groovy Script support plugin
• Legacy Maven 2 Project Plugin
• Maven 3 Plugin
• REST plugin
• SSH Slaves plugin
• Subversion Plugin
• Translation
• Windows Slave Plugin

Recommended Plugins

The following plugins are widely used plugins and are tested as part of the QA certification process

• active-directory
• artifactory
• backup
• batch-task
• build timeout
• checkstyle
• clover
• cobertura
• copy-artifact
• dashboard-view
• deploy
• disk usage
• downstream-buildview
• dry
• email-ext
• emma
• extended-read-permission
• findbugs
• ftppublisher
• gerrit
• global-build-stats
• htmlpublisher
• jacoco
• jira
• jobConfigHistory
• log-parser
• mercurial
• parameterized trigger
• pmd
• postbuild-task
• project-health-report
• promoted builds
• release
• scp
• sonar
• ssh
• svn-tag
• tasks
• violations
• warnings
• ws-cleanup

Other Plugins

All other plugins in the Hudson Plugin Central are not QA certified. However, these plugins are auto tested to load correctly in Hudson.

How to install plugins

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
• Source code copyright