Today we’ll tell you about a command-line tool that helps to make upgrading a store with a lot of third-party extensions way easier. Upgrade Compatibility Tool analyzes the store based on Adobe Commerce, checks all the installed modules, and returns a list of issues that should be resolved to make upgrading to the latest version of Adobe Commerce as smooth as possible.
The typical workflow for the system upgrade using this tool is following:
First of all, the Tool should be downloaded from the repository and executed on the newest release of Adobe Commerce. It is possible (and sometimes even recommended) to run it on the latest beta version to have more time for preparations and upgrade as soon as the system is out of beta.
Then a non-modified instance for the currently installed version of Adobe Commerce should be generated. Later it allows seeing which areas modified by customizations are broken and calculate a complexity score. The latter can be used to understand how difficult the upgrade would be and how much time is required. The detailed information can be found in the developer guide.
After that, the detailed timeline and cost needed for fixes and adjustments can be calculated, so the changes and fixes can be implemented, tested, and released, thus making the store ready to move to the new version as soon as possible.
Also, it is important to consider the system requirements to use the Upgrade Compatibility tool. They are as follows:
Today we’ll tell you about a command-line tool that helps to make upgrading a store with a lot of third-party extensions way easier. Upgrade Compatibility Tool analyzes the store based on Adobe Commerce, checks all the installed modules, and returns a list of issues that should be resolved to make upgrading to the latest version of Adobe Commerce as smooth as possible.
The typical workflow for the system upgrade using this tool is following:
First of all, the Tool should be downloaded from the repository and executed on the newest release of Adobe Commerce. It is possible (and sometimes even recommended) to run it on the latest beta version to have more time for preparations and upgrade as soon as the system is out of beta.
Then a non-modified instance for the currently installed version of Adobe Commerce should be generated. Later it allows seeing which areas modified by customizations are broken and calculate a complexity score. The latter can be used to understand how difficult the upgrade would be and how much time is required. The detailed information can be found in the developer guide.
After that, the detailed timeline and cost needed for fixes and adjustments can be calculated, so the changes and fixes can be implemented, tested, and released, thus making the store ready to move to the new version as soon as possible.
Also, it is important to consider the system requirements to use the Upgrade Compatibility tool. They are as follows:
The detailed information about setup and configuration can be found in the Adobe Experience League guide.
Recent Posts
About Me
Zest Logic
Building custom eCommerce systems for startups, growing IT businesses, and eCom enterprises since 2006.
Popular Post
Oberlo – a dropshipping app for Shopify,
May 23, 2022Splitit launches an Installments-as-a-Service platform.
May 19, 2022PHP 8.1.6 became available.
May 16, 2022Instagram Feeds
zestlogic
Popular Tags