...

You can choose to upgrade only Kiuwan On-Premises clients as long as their latest versions are compatible with your currently installed Kiuwan core. The upgrade process will check this for your and stop the upgrade if your current Kiuwan core is not compatible with the latest available clients.

Kiuwan On-Premises clients are those Kiuwan products that your Kiuwan On-Premises servers will provide to your users:

...

• Kiuwan Jenkins plugin: downloadable from the Jenkins plugin repository.
• Kiuwan Microsoft TFS Azure extension: downloadable through the Azure DevOps marketplace.

Choose this upgrade mode ifwhen:

• New versions of Kiuwan On-Premises clients are available.
• You want to upgrade your installation to make your Kiuwan On-Premises servers provide the latest available versions of each client.
• You want to keep your Kiuwan services untouched.

...

Do not mix up what a Kiuwan On-Premises client version is. These are different concepts:

...

• .

Full mode

The full mode upgrade will upgrade both Kiuwan On-Premises clients and Kiuwan core services.

Keep in mind that when choosing this mode you should always download a new the latest kiuwan-cluster version available. The latest version is always available hereaccessible through this link: https://static.kiuwan.com/download/onpremise/kiuwan-cluster.tar.gz.

Choose this upgrade mode when:

• You want to upgrade your Kiuwan On-Premises clients but your Kiuwan core services version is not compatible with the latests client versions.
• You want to have the latest fixes and features available in Kiuwan.

Upgrade: common steps

Either if you are upgrading only clients or performing a full upgrade, your must follow these steps before starting the upgrade process.

...

Step 1: run the clients upgrade

Open a terminal to the host where you downloaded and run your Kiuwan On-Premises host and locate the kiuwan-cluster tool you used to install Kiuwan On-Premises.

Change and change the directory to where the tool was untared (this directory is referred as [INSTALLER_DIR] in the Kiuwan On-Premises Distributed Installation Guide).

Once the current directory is [INSTALL_DIR], execute this command:

...

• Users will not be able to access Kiuwan On-Premises web application.
• Analyses can be still run and will be queued until the new version is available.

Once the upgrade is finished, all services will be automatically restarted and you will be able to access Kiuwan On-Premises after a while.

Step 1: keep your old kiuwan-cluster installer

 Your current installer may be needed in order to perform some maintenance tasks. It is usually a better idea to keep your current kiuwan-cluster version just in case you need to access it.

Step 2: download kiuwan-cluster latest version

In order to upgrade to the latest versions of Kiuwan On-Premises images you need to download the latest version of the installation tool. Run this in your Kiuwan On-Premises host:

wget https://static.kiuwan.com/download/onpremise/kiuwan-cluster.tar.gz

This will download the latest available installation tool to the current directory.

Step 3: untar kiuwan-cluster

Once downloaded, you should untar the provided gz file:

tar xvzpf kiuwan-cluster.tar.gz

This will untar the installation tool to a folder with extended version information of the tool. For example:

/home/user/kiuwan-cluster_master.XXXX-2.8.YYMM.V

This folder will be referred to as [INSTALL_DIR] throughout the following steps. 

Step 3: check if you need to follow specific steps for your Kiuwan On-Premises version

...

Step 4: run the full upgrade

Change the directory to [INSTALL_DIR] and execute this command:

sudo ./update-full.sh

Updating Apache load balancer configuration

Kiuwan On-Premises installation tool will not update automatically your load balancer configuration, so changes in this file must be made manually. Refer to the Specific upgrade notes section for information on what changes have been made in this element if you want to keep your installation up to date with the latests features added in the load balancer configuration.

In case you are running the default configuration, you can safely overwrite your configuration, but REMEMBER TO UPDATE "kiuwanDomain" variable to point to your specific Kiuwan On-Premises domain:

cp ./volumes/config-shared/ApacheLoadBalancer/conf/httpd.conf [VOLUMES_DIR]/config-shared/ApacheLoadBalancer/conf/httpd.conf

Once the file has been overwritten, edit it and change this line in [VOLUMES_DIR]/config-shared/ApacheLoadBalancer/conf/httpd.conf:

Define kiuwanDomain kiuwan.onpremise.local

It should point to your specific domain. 

Checking your Kiuwan On-Premises clients installations after upgrading

...

Upgrading from Kiuwan On-Premises 2.8.1910.1

...