Evaluate add-ons for Data Center migration
Add-ons extend what your team can do with Atlassian applications, so it's important to make sure that your team can still use their favorite add-ons after migrating to Data Center. This document provides an overview on evaluating add-ons for a Data Center migration.
Check Marketplace add-on compatibility
Marketplace add-ons tagged with DATA CENTER are written and tested by their developers to run on a multi-node cluster environment. While Atlassian checks to ensure that add-on information is as complete as possible, we don't actively monitor or guarantee any code posted in the Marketplace. Therefore, it is important to run a user acceptance test in your Data Center test environment to ensure that each add-on works as expected. You should be able to identify any unusual behavior quickly. Some customers also choose to uninstall the add-on and make sure the functionality disappears as an additional check that the add-on installs cleanly. If your Data Center migration process includes an application upgrade, you can check add-on compatibility for the target version of the application. Remove any add-ons that are not compatible with Data Center before migration.
Evaluate your custom add-ons
Similar to Marketplace add-ons, you will want to test any custom-built add-ons in your Data Center test environment. You may also choose to develop a custom add-on if your Marketplace add-on is not compatible with Data Center. If your custom add-on is not working properly or you need to develop one for Data Center, you can review the following links for guidance:
- Plugin guide to JIRA high availability and clustering
- How do I ensure my add-on works properly in a Confluence cluster?
- Making plugins compatible with Bitbucket Data Center
You can also use the plugin validator to ensure your Confluence add-ons will work on Confluence Data Center.
Check your add-on usage
Before beginning the process, it's a good idea to check if you are using add-ons whose functionality overlaps with other installed add-ons. You should also check for any unused or infrequently used add-ons. While add-ons provide a lot of extended functionality, tests show that the number of add-ons can impact application performance, so removing unused or seldom used add-ons can help increase your application's performance. Since add-ons can modify different aspects of the application's functionality, there is no quick way to check for add-on usage. Many of our customers rely on manual audits, checking the application logs, and monitoring tools to help identify add-ons that are either not being used.
Check your add-on performance
Add-on performance is a common factor for customers experiencing issues with Data Center. Unfortunately, you may not discover this until the application is in production with a large number of users hitting the application. Where possible, it will be beneficial to performance test the application to evaluate how the add-on, or add-ons, perform. Given that the application will run all installed add-ons and add-ons may have dependencies on one another, some customers choose to stress test the application with all add-ons enabled and then selectively disable them if problems arise. Alternatively, some customers also choose to test add-ons by enabling each one at a time based on their preferred testing approach. You can use the Atlassian Performance Testing Framework to run performance tests on Bitbucket Data Center and Confluence Data Center. For JIRA Data Center, you can use these available tools for performance testing.