Upgrade notes and blockers

While upgrading to a new version, beware of the changes specific to a build version and take appropriate action for any blockers.

Upgrade notes

The upgrade notes list the changes and the important updates for each version that you must know before you upgrade. For a complete list of new features, enhancements, fixes, and deprecation of all releases, see Release Notes.
Affected version Notes
8.1.0
Removed Apache Derby as the default database
Apache Derby is deprecated and no longer shipped with HCL DevOps Deploy (Deploy). You must not use Derby for evaluation and in a production environment.
8.0.1.3
Replaced FlexNet licensing with the HCL Licensing system
The FlexNet licensing system is deprecated and replaced with the HCL Licensing system. You can configure Deploy to use HCL Local License Server or Cloud License Server.
See Licensing and Applying HCL licenses to agents. To set up your license server, refer to the HCL Licensing documentation.
New software download location
You can download the installation files of version 8.0.1.3 and all upcoming versions from the My HCLSoftware (MHS) portal.
7.3.2.8
Replaced FlexNet licensing with the HCL Licensing system
The FlexNet licensing system is deprecated and replaced with the HCL Licensing system. You can configure Deploy to use HCL Local License Server or Cloud License Server.
See Licensing and Applying HCL licenses to agents. To set up your license server, refer to the HCL Licensing documentation.
New software download location
You can download the installation files of version 7.3.2.8 and all upcoming versions from the My HCLSoftware (MHS) portal.
7.3.2
Removal of old plug-in versions stored by the agent
When you upgrade and start an agent, the agent communicates with the server and looks for any plug-ins downloaded earlier. If any such plug-ins are found, they are removed from the system, and a new version of those plug-ins are downloaded automatically.

With this change, security vulnerabilities might be removed from agents that had old insecure versions of plug-ins on them.
7.2.3
About 7.2.3.0.ifix01 and 7.2.3.1.ifix01
As part of Deploy 7.2.3 and 7.2.3.1, the Windows service name for agents are no longer customizable by end-users. The name is auto-generated by the Deploy server. Note that the naming convention of auto-generated Windows service name does not follow the naming convention standards. The versions 7.2.3.0.ifix01 and 7.2.3.1.ifix01 generates the Windows service name correctly.

Note that the ifixes do not provide the ability for users to define the service name. The name is auto-generated with the correct format.

Do not upgrade Windows agents with the now pulled-back 7.2.3 and 7.2.3.1 versions. You must use the ifix releases only. If you have already upgraded your Windows agents with original releases, you should reach out to support to find out how to remediate it.
7.1.2.10
Server/agent version mismatch
An inconsistency exists between the versions of the Deploy server and agent installation files. However, the version mismatch, server 7.1.2.10 and agent 7.1.2.9, does not cause any installation or upgrade problems.
7.1.0
Server logging file update
Logging information is now written to deployserver.out instead of the stdout file.

Upgrade blockers

When you upgrade Deploy to a newer version, the installer checks for compatibility with the version of Deploy that you want to upgrade. At the time of upgrade, you might face blockers that restrict you from upgrading Deploy to a particular version.
Note: You must take appropriate action for blockers of all the versions between your current version and the version to which you choose to upgrade.

The following table lists the blockers specific to each version and the actions you must take for an uninterrupted upgrade:

Affected version Blocker and action to take
8.0.0
FIPS non-compliance
Blocker− If you are upgrading a server that uses Java 8 with FIPS-enabled, the installation is aborted and displays an error stating that FIPS mode is currently not supported. Deploy does not support Java 8. Running a server with Java 11 in FIPS mode is not supported in this release.
Action− Currently, there is no fix for this blocker.
7.3.2
Mandatory requirement for starting the Deploy server with SQL server database
Blocker− If you run Deploy server with the SQL server database, the upgrade aborts with the message:
com.urbancode.ds.UDeployServer - Micrsoft SQL Server setting READ_COMMITTED_SNAPSHOT 
is not ON
com.urbancode.ds.UDeployServer - Before the application can start, READ_COMMITTED
_SNAPSHOT must set to ON by your database administrator. To do this, they must 
execute this statement while there are no other clients connected to the named database:
alter database [test] set read_committed_snapshot on. The statement will not complete
until all other clients disconnect. This is a restriction imposed by Microsoft SQL Server.
Action− Before starting the Deploy server, you must enable the READ_COMMITTED_SNAPSHOT SQL server parameter.
7.3.0
3DES keys not supported
Blocker− If you upgrade Deploy with 3DES keys, the upgrade is aborted. This version includes some changes in the encryption keystore because of which 3DES keys are not supported.
Action−
  1. Create a backup before upgrading to this version. See Backup and recover.
  2. Rotate and delete any 3DES keys using the key rotation tool. See Rotating an encryption key and Deleting an encryption key.
  3. Set a key alias.
Upgrade with Java 11
Blocker− If the current server uses Java 8, the upgrade prompts you to specify Java 11.
Action− You must install Java 11 or later and set the JAVA_HOME environment variable. See System Requirements for a list of supported Java versions. See Changing or updating the JRE of servers for information about updating the JRE on your server.
7.1.1
Migration of JMS agents
Blocker− If you upgrade Deploy with JMS agents, a warning message is displayed. You are prompted to begin the migration of JMS agents to a web format.
Action− You must migrate all JMS agents to the Web. See Migrating agents to Web.
Hibernate v5.4.20
Blocker− In this version, the Hibernate version is updated to 5.4.20. Hibernate version 5.4.20 might require newer versions of the JDBC driver to function properly.
Action− You must ensure that you have the JDBC driver version that works with your database and is compatible with Hibernate 5.4.20. This upgrade also removes the hibernate.dialect property from the installed.properties file as the new Hibernate version itself determines the dialect.