Analyzing and upgrading projects with Spryker Jarvis

Spryker Jarvis is the command-line tool that lets you analyze your Spryker-based project and eventually migrate it to the most up-to-date version of Spryker. The tool helps you quickly get answers to the following questions:

• How outdated is your project compared to the latest Spryker product release?
• What features does your project already use, and what are the other features it could use?
• What should you do to update your project to the latest Spryker product release?
• How did the new Spryker module version affect your project?
• How far are your modules behind the latest Spryker minor and major module versions?
• What features are compatible with your current project version?

Spryker Jarvis is meant mostly for developers working on the Spryker projects who want to get a clear view of what it takes to update their project to the latest product release version of Spryker. The tools can also be useful for project managers, as it answers the question “How outdated is the project?“ and helps to estimate efforts to update the project.

This document shows how to install and use the Spryker Jarvis tool for the analysis and upgrade of your project.

Prerequisites

• Install Spryker project locally
• Install Node.js

Install Spryker Jarvis

1. Fork, clone, or download the Spryker Jarvis repository.
2. Open the terminal and do the following:
   1. Go to the Spryker Jarvis folder.
   2. Run npm install. Now you have Spryker Jarvis installed.

Use Spryker Jarvis to migrate your project

To migrate your project to the latest version of Spryker using the Spryker Jarvis tool, follow these steps:

1. Inside the Spryker Jarvis folder, run the command

node jarvis.js <path to your spryker project folder>

2. Follow the terminal script about your project name.
3. In your browser, open http://localhost:7777 and enjoy the migration analysis.

Jarvis views

Depending on your project’s specifics and your goals, you can use various migration views available in Jarvis and take necessary actions. There are three views:

• Basic view—for migrating to a newer product release.
• No-features view—for upgrading your project modules to their current major and minor versions.
• Missing-features view—for upgrading your project with the compatible Spryker features.

Basic view: Migrating to a newer product release

To migrate to a newer product release, use the Jarvis basic view. This view lists all the Spryker features that require an upgrade to make your project up-to-date with the latest Spryker version. For each feature, the upgraded and the removed dependencies are listed.

This view is especially useful when:

• You have a Spryker-based product and finished the main development part of it.
• Your project uses feature repositories, or the project is based on the Spyker B2B Demo Shop or the B2C Demo Shop.

Use this view if you want to stay up-to-date with Spryker and get new features of every Spryker product release.

To see this view, run node jarvis.js <path to your spryker project folder> in the terminal. This shows you the main Spryker Jarvis page with information about the product release you can upgrade your project to.

It can be that a dependency has been upgraded, but no migration is needed. In this case, we will highlight it:

In this view, under the list of features to upgrade and the dependencies, you can also check the features you don’t use but might be interested in. The recently released features are marked as New feature:

You can go to the repository of each feature by clicking the feature names.

No-features view: Upgrading modules to their current versions

To upgrade your modules to their current major and minor versions, use the no-features view.

This view provides information about modules that have been upgraded to new versions by Spryker.

The no-features view is especially useful when your project does not use any feature repository; you use just modules. This can be the case if your project is in active development or is very old.

Use this view to understand to what extent your project is outdated and estimate the effort to update it.

To see this view, run node jarvis.js <path to your spryker project folder> --no-features in the terminal. This shows you what modules are behind their minor and major versions, and how far they are behind:

To see details on a module, such as, what changes have been made in the later versions compared to your module version, click the module:

The detailed view of modules lets you analyze the changes, and if needed, upgrade the modules. To upgrade to the latest minor module versions, run the module composer update command. To upgrade to a major version, follow the migration guide of the respective module.

Missing-features view: Upgrading your project with the compatible Spryker features

To upgrade your project with the compatible Spryker features, use the missing-features view.

This view shows you what features you can use based on the modules you already have installed. The missing-features view tells you which modules you need to install to enable the respective Spryker features. So with this view, you can quickly identify what you need to do to replace separate modules with full-fledged features compatible with your project.

The missing-features view is especially useful when your project uses just Spryker modules and does not use the Spryker features, but you want to use them. If you want to start keeping your project up-to-date with the Spryker product release, but you do not know which Spryker features of which versions are compatible with your project, this the right view.

To see this view, run node jarvis.js <path to your spryker project folder> --missing-features in the terminal. This shows you which modules of which features you have installed and what modules you still need to install to be able to use those features. This page tells you which highest versions of the features you can replace the modules with and what integration guide you should follow to enable the respective features:

In most cases, you need to add missing dependencies to your project to be able to use the Spryker features. But sometimes, you can swap your modules with the Spryker features because your project already has all the dependencies, as in this example:

Current constraints

For now, you can not do the following things with Jarvis:

• In the no-features view, the starting point for module updates is not provided. So as of now, the tool does not tell you which module to update first.
• For the basic view, if you use the old Legacy Demoshop, there is no migration path. To migrate such projects, an individual approach is needed. The same is true if you use an old technology of Spryker, like collectors that have been replaced with Publish&Synchronization.

Reference

To see Spryker Jarvis in action, check out this video: