Updating the Universal Plugin Manager

Like other add-ons, the Universal Plugin Manager (UPM) receives regular software updates to incorporate bug fixes and enhancements. We recommend keeping UPM updated to the latest version, regardless of the version of your host application.

If you use UPM 1.6 or later, you can update the UPM directly from the Manage add-ons page. If UPM is running in online mode (connected to the Atlassian Marketplace, that is), it automatically reports when an update is available. You'll see a notification at the top of the Manage add-ons page when an update is available.

If you run UPM behind a firewall or in offline mode, you can also install updates directly using the latest JAR file from the Marketplace.

If your application is clustered (for example Data Center applications) you will need to perform a rolling restart of your cluster to make sure the new version of UPM is propagated correctly to all nodes.

On this page:

Checking your UPM version

You can validate your version of UPM from the version number at the bottom of any add-on administration page, like the Manage add-ons page. 

You'll see something like this: 

Checking your UPM version

Updating UPM in online mode

To update the UPM in online mode, ensure you're logged in with admin privileges. From there: 

  1. Click the Manage add-ons link in the administration menu.  
    If a later version of the UPM software is available, you'll see an update banner at the top of the page.  


    The content of the UPM update banner varies slightly between different versions of the UPM. In every case, however, the banner includes a link for updating the UPM software.

  2. Click Update now automatically download and apply the update.
    You don't need to restart the application after the update. For certain version updates, you'll need to refresh the browser page, as indicated by an onscreen message.

In UPM 2.7.4 and later, the banner offers links for three options:

  • Update now: immediately downloads and applies the update to the UPM software.
  • Skip this update: keeps the current version of the UPM software and suppresses future reminders about the availability of the current latest version. The reminder appears when subsequent versions become available.
  • Remind me next time: closes the banner for now, but it will appear again the next time you go to the 'Manage Add-ons' page. 

Updating UPM by file upload

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 applications, Confluence, FishEye or Crucible from versions 1.5 and earlier.

To update the UPM:

  1. Download the latest version of the UPM software from the Atlassian Marketplace.
  2. As a user with administrator privileges, go to the add-ons administration page. For older versions of the UPM, you can do this by clicking the Plugins link in the administration menu.
  3. Navigate to the Install tab.
  4. Click Upload plugin or Upload add-on.
  5. In the file chooser, browse to and select the UPM JAR file that you downloaded.
  6. After selecting the UPM JAR file, press Upload to apply the update.
    A dialog appears indicating that the installation is being performed.

    Depending on the UPM version you are replacing, it's possible for the UPM update to appear to fail. This may take one of several forms: the install progress dialog may appear to hang, or it may close quickly, or it may finish and show 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.

  7. 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.

Updating UPM by file replacement

If for any reason you cannot update UPM through the administration page, you can update UPM file by replacing the UPM file in the directory instead. Before starting, get the version of the plugin that you want to install from Atlassian Marketplace. Then follow the instructions appropriate to your application.

JIRA applications

To update the UPM file on disk in JIRA applications:

  1. Shut down the application.
  2. Remove the existing UPM JAR file from this directory in your JIRA home directory: 
    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
  3. Copy the new UPM JAR file into the same directory.
  4. Restart your JIRA application.

Confluence

Confluence stores add-ons such as UPM in its database, so the process for updating it by file replacement is a little different to other products.

To update the UPM file in Confluence:

  1. Download the UPM JAR from the Atlassian Marketplace
  2. Stop Confluence. 
  3. Remove the existing UPM JAR file from <install-directory>/confluence/WEB-INF/atlassian-bundled-plugins
  4. Copy the new UPM JAR file into the same directory. 
  5. Clear the Confluence plugins cache
  6. Restart Confluence.

FishEye

To update the UPM file on disk in FishEye:

  1. Shut down your FishEye instance.
  2. Using an archive management tool, open the following archive in your FishEye installation directory: 
    plugins/bundled-plugins.zip 
  3. Delete (do not extract) the existing atlassian-universal-plugin-manager-plugin-x.x.x.jar from the ZIP file.
  4. Add the new plugin version from the folder it was downloaded to into the zip file.
  5. Close the ZIP file.
  6. Delete the following file from you FishEye installation directory: 
    var/plugins/bundled/atlassian-universal-plugin-manager-plugin-x.x.x.jar
     file.
  7. Start your instance again.

Stash/Bitbucket Server

To update the UPM file on disk in Stash/Bitbucket Server:

  1. Shut down Stash/Bitbucket Server.
  2. Remove the existing UPM JAR file from this directory in the Stash/Bitbucket Server home directory: 
    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
  3. Copy the latest UPM JAR file into the same directory.
  4. Restart Stash/Bitbucket Server.

Bamboo

To update the UPM file on disk in Bamboo:

  1. Shut down Bamboo.
  2. Remove the existing UPM JAR file from the plugins/ directory in the Bamboo home directory.
    The name of the JAR file may be prepended with a number, such as:
    846688264762062110.atlassian-universal-plugin-manager-plugin-2.7.6.jar
  3. Copy the latest UPM JAR file into the same directory.
  4. Restart Bamboo.

Downgrading UPM versions

If you run into problems after updating the UPM software, you may need to revert the software to the earlier version. The procedure for downgrading UPM is the same as it is for updating UPM by replacing the UPM JAR on disk. If you already have the JAR file of the UPM version to which you want to revert, follow the instructions for updating UPM by file replacement to apply it to your application.

If you don't have the UPM JAR file for an earlier version, you can get it from the version history section of the Universal Plugin Manager listing page on the Marketplace.

Last modified on Oct 24, 2017

Was this helpful?

Yes
No
Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.