Release and Deploy Pre-upgrade Guide

Overview

To best ensure a successful upgrade, we recommend the following approach in testing.

Expectations from Testing

• You have gone through all the Release manuals between the current version and the version you are planning to upgrade
• The test is conducted on the lower Environment and the DB backup of production DB for both of the tools
• The lower environment has been configured as closely as possible to the production environment, e.g. security settings, SSL, use of Load balancers, plugins and extensions like Satellite, and mock versions of the release pipelines for at least the most critical applications.
• Pipelines are tested for any change in the behavior,; the same applies to the User management/access control/New feature/API change.
• Testing of any customization that would not be tested by Digital.ai, such as custom plugins/settings, because the maintenance of these plugins is solely the customer's responsibility. Check release notes for any API changes that could impact these customizations. If you are in doubt, you can always reach out to your Customer Success Manager for assistance.

The day before the upgrade

During the upgrade process, enable maintenance mode (for all versions of Deploy and recent versions of Release) to avoid picking any new tasks and complete existing releases

• In Release, login as Admin, archive as many releases as you can (if completed/aborted/Done), and clean any dangling/dormant releases (xl-release)
• In Deploy, login as an Admin, Run archive policies to archive any dangling jobs 
• Check the Deploy task monitor as attached; you shouldn't see any tasks under Monitoring > Deployment task or Monitoring > Control task 
• Please shutdown xl-release/xl-deploy completely before taking DB backup and XLR/D_home