1.4. Update and Migration

The information about changes to the Axivion Suite is located in the ChangeLog.txt. This file comes with each installation of the Axivion Suite and is located in the installation directory.

If you are using a separate installation of the Axivion Suite for a centralized Dashboard installation, you can upgrade that installation first and everything should continue to work unless otherwise noted in the respective migration chapter. The Dashboard is designed to be backwards compatible and thus can display the analysis results produced by older installations of the Axivion Suite. It will not do any automatic migration of the analysis data either, so you can continue analyzing with an older version of the Axivion Suite and still display the results in a newer Dashboard.

Users of the IDE plugins usually are not required to upgrade immediately. Once the Dashboard they are working with is upgraded, they can download the updated version from the upgraded Dashboard.

Before you install a new version of the Axivion Suite :

  • Make sure you have a backup copy of all user data (e. g., databases), customized scripts, and configurations.

  • Make sure you have closed all applications coming with the Axivion Suite .

  • Make sure you have shut down all running dashboard servers.

  • Make sure all continuous integration tasks are completed.

  • Make sure you have uninstalled the previous version of the Axivion Suite completely.

  • Make sure you do not have files in the installation directory shadowed in your VirtualStore (if you are using a version of Windows that uses VirtualStore).

Note

It is in general a good idea to use project configurations and a separate directory for your own scripts or those scripts that have been altered for your environment.

Caution

It is in general a bad idea…

…to place user data into installation directories;

…to manually change scripts in the installation directories without having a copy for restoring these scripts in the future.

Some migration steps need changes in customized scripts or migration steps for the continuous integration database.

Maybe you applied patches to scripts and configurations that are not necessary with a newer version of the Axivion Suite . Please make sure to cross check those files for necessity with the new version of the Axivion Suite .

Please make sure to review the ChangeLog.txt for the version leap you are planning.

Caution

We do not list all potentially necessary changes in the build process of your projects under Erosion Protection here because this information is contained in the ChangeLog.txt.

Caution

You are advised to make a dedicated backup copy of your database and run an continuous integration cycle using the new version of the Axivion Suite in order to check the operability. Cross check that changes in the Erosion Indicators are due to new functionality or bug fixes.

We strongly recommend the following process for upgrading (i. e. this minimizes the amount of removed/added issues seen in the dashboard):

  • Before you install the new version of the Axivion Suite :

    • Pin down a current version of the system under analysis guaranteed to build with the native build process.

    • Run a complete CI cycle.

    • Cross check the CI protocol: are there messages indicating a missing configuration or some error condition?

  • Proceed with the installation of the new version as advised in the beginning of this chapter.

  • After you have successfully installed the new version of the Axivion Suite :

    • Run a second complete CI cycle using the same version as pinned down previously.

    • Cross check the CI protocol: are there messages indicating a missing configuration or some error condition?

    • Cross check the changes in erosion indicators using the dashboard.