This page only applies to deployments using the develop branch for early access to new features. Deployments tracking feature releases should not follow the instructions on this page.
When upgrading Registry while tracking Develop, it can be tricky to understand what intermediate steps must be taken based on where a given deployment is and wants to get to. Ordinarily, the upgradeVersion command handles the steps that do not require manual intervention, however when tracking develop it may be necessary to run these steps manually.
How To Use This Page
The instructions on this page assume the deployment was previously and successfully upgraded to the most recent feature release. For example, if the next scheduled feature release is v4.1.0, the deployment should have previously (at some point) upgraded to v4.0.0.
Before upgrading the deployment, first note what commit the deployment is currently at. If the deployment was at a release, the commit is available via this list. For convenience, this will be referred to as the origin commit. Then note what commit the deployment will be upgraded to. This will be referred to as the destination commit.
Read through the relevant tasks below before upgrading. In most cases, the tasks must be run after installing the updated code and updating the database schema, but there may be exceptions.
This page is grouped by Registry release. Find the section associated with the most recent release the deployment was upgraded to. This should generally be the first section, below; information for other releases is generally maintained for historical reference only.
Within the appropriate section, start at the top and find the first commit later than the origin commit. If there is no such commit, no actions need to be taken. Continue working down the list until reaching a commit that is later than the destination commit. Ordinarily, this will be all remaining tasks in the section.
94a3c46e11: Populate EnvSource duplicate_mode
Create a Duplicate Mode setting for each instance of EnvSource. The easiest way to do this is via SQL:
SQL> update cm_env_sources set duplicate_mode='SI' where duplicate_mode is null;
Alternately, review each EnvSource configuration and make an appropriate selection.