Updating Self Managed Commerce

To update an existing Self Managed Commerce stack with new code and data, use the Jenkins deploy-or-delete-commerce-stack job.

Procedure

note

If you have your Self Managed Commerce set up with an author and a live environment ensure that you apply steps 3 and 4 for each of these environments. A pair of author and live environments should always remain at the same code level.

1. Run the Jenkins job build-deployment-package with the epCommerceBranch job parameter set to the desired Self Managed Commerce branch.

   For more information about this job, see Building the Deployment Package.

2. Run the Jenkins job build-selected-docker-images to build the new Self Managed Commerce images. Make sure to use a unique value for the imageTag job parameter and that the following images are selected to be built:

   • Commerce Manager
   • Integration
   • Search
   • Cortex
   • Batch

   For more information about this job, see Building the Commerce Container Images.

3. Run the Jenkins job run-data-pop-tool on the Self Managed Commerce environment with the dataPopToolCommand job parameter set to update-db.

   For more information about this job, see Populating the Database.

4. Run the Jenkins job deploy-or-delete-commerce-stack.

   You can use the original build that created your environment to rebuild the job. You must set the dockerImageTag job parameter to the value of the imageTag job parameter from step 2. If you have not updated the image tag value, you will need to specify restartApps, which will perform a rollout restart on the Self Managed Commerce deployments.

   note

   We recommend that you run the Jenkins job deploy-or-delete-commerce-stack with the plan_mode job parameter set to true when updating the environment. This requires you to review and approve of the changes before they are applied to the environment.

   For more information about this job, see Deploying Self Managed Commerce.