Upgrading the Tool

The DevKit Pipeline tool can be upgraded.

The tool can be upgraded from v1.0.1 to v1.0.2.
The tool can be upgraded from v1.0.1 or v1.0.2 to v1.0.3.
The tool can be upgraded from v1.0.1, v1.0.2, or v1.0.3 to v1.0.4.
The tool can be upgraded to v1.1.

Prerequisites

The DevKit Web tool, DevKit CLI tool, Compatibility Testing tool, or Java Performance Testing tool has been installed on the server.

Procedure

If you need to upgrade the DevKit Web tool, DevKit CLI tool, Compatibility Testing tool, or Java Performance Testing tool, uninstall the tool following instructions in Uninstalling the Tool, and then install the new tool version following instructions in Batch Installing Tools. If other tools remain unchanged, they do not need to be upgraded.

**Table 1** Change description
Tool	Description
DevKit Web tool	Can be upgraded from 24.0.RC1 or 24.0.RC2 to 24.0.RC3. Can be upgraded to 24.0.T50.
DevKit CLI tool	Can be upgraded from 24.0.RC1 to 24.0.RC2. Changed the run-check command for 64-bit running mode check to the run-mode command. Changed the byte-align command for byte alignment check to the addr-align command. Changed the mem-cons command for memory consistency check to the mm-check command. Changed the constr-check command for build affinity check to the affi-check command. Added the function of generating BC files. Can be upgraded from 24.0.RC2 to 24.0.RC3. Added the -c option to 64-bit running mode check. Deleted the -b option from byte alignment check. Deleted the -b option from build affinity check. Can be upgraded to 24.0.T50. Modified the description of memory consistency check and vectorization check.
Compatibility testing tool	Can be upgraded to v2.1.
Java Performance Testing tool	Can be upgraded to v1.1.