When planning an update to Atlassian application software, you can check the compatibility of your installed plugins with the target application version. This helps you identify potential plugin compatibility issues before you start the update. In general, you should carefully test updates in a staging environment before deploying to production. But using the plugin update check can help save time and effort during the update.
The update check feature is available in the host application only if it is in online mode and can contact the Atlassian Marketplace web site. When performing the check, the application requests plugin compatibility information from the Atlassian Marketplace. The Marketplace can provide useful information only for those plugins for which version compatibility information exists.
Checking plugin compatibility
To check compatibility of your plugins:
- As a user with administrator privileges in the application, navigate to the application update check page.
The page name varies by host application. For example, in JIRA the page is named 'JIRA Update Check'; in Confluence, it is named 'Confluence Update Check'. - In the Check compatibility for update to menu, select the version against which you want to check plugin compatibility.
The menu displays all software versions released since the current version.
- Click the Check button.
The UPM performs the check and shows the results on the page. You can click the name of any plugin to view more information for that plugin.
バージョンの互換性の確認結果
After performing the compatibility check, the UPM provides results by listing plugins into the following categories:
- Incompatible – The installed versions of these plugins are not compatible with the selected application version. There are currently no plugin updates available that are compatible with the selected application version.
- Compatible, if updated – The installed versions of these plugins are not compatible with the selected application version. However, the plugins will be compatible if you update them. There are buttons allowing you to update these plugins.
- Compatible once both <the application> and the plugin are updated – The installed versions of these plugins are not compatible with the selected application version. There is a plugin compatible with the newer application version, but it is not compatible with the application version you are currently running. You must update the application and then update the plugin. There are buttons allowing you to disable these plugins before proceeding with the update.
- Compatible – The currently installed versions of these plugins are compatible with the selected application version.
- Unknown – These plugins may or may not be compatible with the target application version. If a plugin is not registered with the Atlassian Marketplace, the Universal Plugin Manager cannot check its version compatibility.
A sample result page appears as follows:
概要
コンテンツ ツール
アプリ
Log a request with our support team.
Raise an issue for our developers.
See answers from the community.
Tweet, blog and update our documentation.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.
1 Comment
Roystine Machado
Feb 20, 2017Should we disable the "incompatible" plugins before upgrade.
what if we have performed the upgrade and facing "JIRA startup failure.
this is the result of the JIRA update check of our production instance (same as the dev instance).:
Incompatible :
FishEye Plugin
JIRA Agile
JIRA SUbversion plugin
Wallboard Plugin
Compatible if updated :
SQL for JIRA custom fields
SQL for JIRA reports and gadgets
COmpatible once both JIRA and the add-on are updated :
Atlassian Universal Plugin Manager Plugin
Database Custom Field
Email This Issue Plugin
JIRA Calendar Plugin
JIRA Suite Utilities
katl-commons
Subversion ALM
Unknown :
valiantys-base-plugin
please help resolve the issue