Warning: We are moving Exalate for HP QC/ALM into basic maintenance mode. This transition period will last until November 2024, after which support will be halted completely. For more information, please see https://exalate.com/blog/end-of-support-hp/.
This article describes how you can upgrade the Exalate application for HP ALM/QC.
Exalate has an advanced transaction-based synchronization engine where every change is recorded and queued such that it is applied in the correct order.
It means that the upgrade is safe and you won't lose any data. The synchronization is resumed from the moment it stopped.
Note: Use the terminal to interact with the server, where you have the Exalate application for HP ALM/QC installed.
Upgrading Docker Image
- Navigate to the directory with the Exalate app for HP ALM/QC installed
cd ~/exalate-hp-qc
- Stop the Exalate application
docker-compose stop
- Remove the previous version and replace with the latest one
cat docker-compose.yml | tee docker-compose.yml.bak | sed -e "s@idalko/hpqcnode:.*@idalko/hpqcnode:5.0.13@g" | tee docker-compose.yml
Warning: You need to replace 5.0.13 in "s@idalko/hpqcnode:.*@idalko/hpqcnode:5.0.13@g" for the latest version, you're upgrading to. Check the release history for more details.
- Start the Exalate application
docker-compose up -d
Upgrading RPM Package
Note: You can download the latest application version here.
- Stop the Exalate application
/etc/init.d/hpqcnode stop
- Remove the previous version and replace with a new one
yum remove exalate-hpqcnode-4.3.0.noarch.rpm && yum localinstall exalate-hpqcnode-5.0.13.noarch.rpm
- Compare /etc/init.d/hpqcnode.dist with /etc/init.d/hpqcnode and merge if there are differences
- Start the Exalate application
/etc/init.d/hpqcnode start
Have more questions? Ask the community