Introduction

This document serves as a quick reference on how to upgrade to a new ICM version. 

References

• Overview - 7.10 Patch Migration
• Cookbook - Deployment Tools ICM 7.10
• Cookbook - Setup CI Infrastructure

Prerequisites

Intershop recommends to set up a Git repository and to use a "standard" branch to check in the updates. This makes it easier to see changes and merge them to your customization.

This should be set up from the beginning. 

1. Create a "standard" branch.
2. Add the Responsive Starter Store.
3. Create the master/develop branches - as you want.
4. Update the "standard" branch with Responsive Starter Store updates.

Steps

1. Download the new Responsive Starter Store.
   The Responsive Starter Store can be found at Intershop Product Resources | Reference Applications | Responsive App.
2. Check if there are changes in the source of the Responsive Starter Store caused by customizations:
   
   1. If there are no changes done caused by customizations, then you can replace it with the new one. This would be the case if your customizations are completely done in your own cartridges.

   2. If there are changes, merge your changes into the new Responsive Starter Store. At the end, the merged new responsive starter store will replaces the old one.

      Info

      Intershop recommends to use another assembly name:

      • You will not get in conflict with artifacts of the original assembly
      • You have your own version number
      • On deployment you see that you deployed your own assembly
      • You can deploy the standard assembly with the same repository
3. Merge your changes into the new versions of build.gradle, especially, the build.gradle of the root and the assembly.
4. Migrate/merge customizations done independent from the Responsive Starter Store.
5. Run gradlew build, publish and deployServer (deployServer includes the first two).
6. Once the server is deployed correctly, do a DBmigrate.
7. Test the installation.
8. If everything works as intended, then you can publish a release or snapshot to the Nexus.
9. Deploy it on a test system.
10. A DBMigrate must be done here for every installation that has an own DB schema and also for the production environment.
    For the production environment it is better to have the dump imported into a test system and do a migrate here and the ex/import it back to the production system.