content_image/713598.jpg
## Removing a plugin 

When a plugin is no longer used in a Jenkins environment, it is prudent to remove the plugin from the Jenkins master. This provides a number of benefits such as reducing memory overhead at boot or runtime, reducing configuration options in the web UI, and removing the potential for future conflicts with new plugin updates. 

## Uninstalling a plugin 

The simplest way to uninstall a plugin is to navigate to the Installed  tab on the Manage Plugins page. From there, Jenkins will automatically determine which plugins are safe to uninstall, those which are not dependencies of other plugins, and present a button for doing so. 

<img src='content_image/713598.jpg'>

A plugin may also be uninstalled by removing the corresponding .hpi  file from the JENKINS_HOME/plugins  directory on the master. The plugin will continue to function until the master has been restarted. 

## CAUTION 

If a plugin .hpi  file is removed but required by other plugins, the Jenkins master may fail to boot correctly. 

Uninstalling a plugin does not  remove the configuration that the plugin may have created. If there are existing jobs/nodes/views/builds/etc configurations that reference data created by the plugin, during boot Jenkins will warn that some configurations could not be fully loaded and ignore the unrecognized data. 

Since the configuration(s) will be preserved until they are overwritten, re-installing the plugin will result in those configuration values reappearing. 

## Removing old data 

Jenkins provides a facility for purging configuration left behind by uninstalled plugins. Navigate to Manage Jenkins  and then click on Manage Old Data  to review and remove old data. 

