The Universal Plugin Manager (UPM) is itself implemented as a plugin. Like other plugins, the UPM is subject to regular software updates, which typically incorporate enhancements and bug fixes. In general, Atlassian recommends that you have the latest version of the UPM installed in your application, regardless of the application version.
You can apply updates to the UPM software directly from the Manage Plugins page in the Atlassian application. UPM versions 1.6 and later are capable of updating to newer UPM versions.
You can update the UPM software with a single click or, if the application is in offline mode, by acquiring the latest UPM JAR file and manually uploading it to your application instance.
On this page:
If the Atlassian application instance is connected to the Internet, it automatically checks whether a more recent version of the UPM is available and presents a notice on the page if so.
You can see what version of the UPM software is currently running by checking the version number at the bottom of the plugins administration page.
To update the UPM software to its latest version from the UPM interface:
Note that the content of the UPM update banner varies slightly between different versions of the UPM. However, the banner should include a link for updating the UPM software.
In UPM 2.7.4 and later, the banner offers links for three options:
If not connected to the Internet or in certain troubleshooting scenarios, you may need to update the software by uploading the UPM JAR file to the Atlassian application. You need to follow these steps to update the Universal Plugin Manager for JIRA, Confluence, FishEye or Crucible from versions 1.5 and lower.
To update the UPM:
Press Upload to apply the update.
A dialog appears indicating that the installation is being performed.
Depending on the UPM version you are replacing, the installation process may appear to fail in various ways, such as appearing to hang, returning immediately, or by finishing and showing an error message. In most cases, the installation actually succeeds, but appears to fail due to issues with older UPM versions. If you think you have encountered this situation, wait a few minutes for the installation to finish and then refresh the browser. Check the footer at the bottom of the page to verify the UPM version.
When prompted, refresh the browser or restart the application.
If you are updating the UPM in Confluence 3.4.x, you need to restart Confluence a second time. (See bug report CONF-22323. Note that this bug affects Confluence versions 3.4.x only.)
The UPM version is now up-to-date.
If for any reason you cannot update UPM through the Atlassian application administration page, you can update UPM file by replacing the UPM file in the directory instead.
This procedure also applies if you need to revert UPM to an earlier version. This is the only way to revert UPM to an earlier version.
Before starting, get the version of the UPM plugin that you want to install from Atlassian Marketplace. Then follow the instructions appropriate to your application.
JIRA
To update the UPM file on disk in JIRA:
plugins\installed-plugins
846688264762062110.atlassian-universal-plugin-manager-plugin-2.7.6.jar
Confluence
Confluence stores plugins, such as UPM, in its database. Rather than attempting to remove the plugin from the database, you can use the Confluence plugin servlet, which presents a secondary web interface for managing plugins.
To update the UPM file in Confluence:
Go to this URL on your Confluence site:
http://<confluence_site>/admin/viewplugins.action
The installed version of the Confluence Plugin Manager appears.
FishEye
To update the UPM file on disk in FishEye:
plugins/bundled-plugins.zip
atlassian-universal-plugin-manager-plugin-x.x.x.jar
from the zip file.
var/plugins/bundled/atlassian-universal-plugin-manager-plugin-x.x.x.jar
file.Stash
To update the UPM file on disk in Stash:
plugins\installed-plugins
The name of the JAR file may be prepended with a number, such as:846688264762062110.atlassian-universal-plugin-manager-plugin-2.7.6.jar