Overview
New in version 2.0, pulse™ now supports extension via plugins. Plugins can be used to add support for new tools to pulse™, e.g. a new testing library.
Plugin Management
Users with administrative privileges can manage plugins via the "plugins" tab of the "administration" of the web interface. This tab shows the installed plugins and their current state.
Installing and Uninstalling Plugins
To install a new plugin, you have two options:
- Shut down pulse™ and drop the new plugin jar file in the $PULSE_DATA/plugins directory. The plugin will be discovered automatically when pulse™ is restarted. This is the only way to install a plugin on an agent at present.
- Click the "install new plugin" link at the bottom of the "all plugins" table in the web interface. This allows you to either upload the plugin jar from your local machine, or enter its path if it is already on the pulse™ master filesystem.
To uninstall a plugin, you should mark the plugin for uninstallation in the web interface using the "uninstall" link. Note that the plugin will not be uninstalled immediately: it will be removed next time pulse™ is restarted. Note if the plugin has any dependents then they will no longer load after the plugin is uninstalled.
Disabling Plugins
To prevent a plugin from being loaded, but keep the plugin jar file in place, the plugin should be disabled. You can do this by marking the plugin for disable with the "disable" link in the web UI. The plugin will then be disabled when pulse™ is next restarted. Note that if the plugin has dependents then they will no longer load until the plugin is reenabled.
Plugins and Agents
Note that currently you need to manually ensure that all agents have the plugins they require to execute the builds dispatched to them. In particular, if you install a new build-time plugin on your pulse™ master, you should also install it on your agents.
Plugin Development
If you are interested in developing plugins for pulse™, refer to Plugins page.
