At the present time upgrading Continuum is a manual, decision based process. The upgrade process is quick and painless, but does require an outage. This means that you will need to select a period of downtime where pipelines, automation, user logins, etc. may be interrupted. Usually this period of time is seconds, not minutes. Our goal is to get to a zero downtime upgrade in the future.
If the Continuum server does not have direct outbound access to the internet you will need to download the file to the Continuum server using an intermediate step such as your desktop, then get the file to the server using sftp or some other protocol.
Versions older than 18.2.1, will need an upgrade to 19.0.2 before upgrading to 19.1.0.
As of 19.1.0 Single Server Mode is now set via the UI and not stored in the Continuum.yaml file. The setting is in Administration ->Settings->System->Single Server Mode. This is set to true after upgrades or installs.
Download the Upgrade File
You may have received an email with a link to download the latest release of Continuum. Use this link in the following command.
curl -O "download link here"
Or if you prefer
wget -O "download link here"
Run the Upgrade
NOTE: make sure you run the following steps as the Continuum application owner on the Continuum server.
# make the installer executable chmod +x downloadedfile # run the executable, using silent mode (no prompting) ./downloadedfile
The upgrade process performs the following actions:
Stops the Continuum services
Installs the new files into a new directory under $CONTINUUM_HOME (usually under /opt/continuum)
Changes a symbolic link /opt/continuum/current to point to the new directory
Performs any database change scripts that may be included
Restarts the Continuum services
At this point you should be able to log back into the Continuum application and its service is returned to normal.
Rolling Back to a Previous Release
If for any reason you need to rollback to a previous release, you can use the following commands to perform the rollback.
NOTE: replace the versioned directory name in the third command below with the proper directory name that you want to rollback to.
ctm-stop-services rm /opt/continuum/current ln -s /opt/continuum/ctm-1.47.410-x86_64 /opt/continuum/current ctm-start-services
Login and check your data.
At this time there is no way to rollback the database version in Continuum. However we make our best effort to make database modification additive so as to not affect previous releases adversely.