...
...
...
Kiuwan On-Premises clients are those Kiuwan products that your Kiuwan On-Premises servers will provide to your users:
- Kiuwan Local Analyzer
- Kiuwan Engine
- Kiuwan for developers IDE plugins or extensions (Eclipse, JetBrains, Visual Studio and Visual Studio Code).
There are more Kiuwan clients that you may need to upgrade, but are provided by external sources and you should follow the standard upgrade procedure of their platform:
- Kiuwan Jenkins plugin: downloadable from the Jenkins plugin repository.
- Kiuwan Microsoft TFS Azure extension: downloadable through the Azure DevOps marketplace.
...
...
...
...
...
...
...
...
...
...
...
...
Step 3: check if you need to follow specific steps for your Kiuwan On-Premises version
Step 4: run the full upgrade
...
...
Specific upgrade notes
This section provides information that you may need to follow in case you are upgrading one of these specific versions (see Checking for updates section if you want to check which version is installed in your company):
Kiuwan On-Premises version | Specific upgrade process needed |
---|---|
2.8.1910.1 | YES |
Upgrading from Kiuwan On-Premises 2.8.1910.1
...
...
Due to changes in how Redis Cluster is created through the installation process, in order to keep your installation up to date with the latest infrastructure you will need to follow a different approach to perform a full upgrade from this version.
You will need both the kiuwan-cluster version you used to install 2.8.1910.1 and the latest available kiuwan-cluster (that can be downloaded here https://static.kiuwan.com/download/onpremise/kiuwan-cluster.tar.gz). We will refer to this locations:
- [INSTALL_DIR_OLD]: where the old kiuwan-cluster version was untared.
- [INSTALL_DIR]: where the new kiuwan-cluster version has been untared.
Note that if you are using AWS elasticache service to run Redis Cluster you can ignore this process and follow the standard upgrade process.
Step 1: stop kiuwan services
*stop-kiuwan.sh (version vieja)
Step 2: update your current configuration
*update.sh (version nueva)
Step 3: prune current containers
*uninstall.sh (version nueva)
Step 4: clean Redis cluster data
...
...
Step 5: update Redis cluster node information
*Cambiar en el fichero globalConfig.properties las direcciones de los nodos de redis.
redis.cache.nodes=172.17.0.1:6379,172.17.0.1:6380,172.17.0.1:6381,172.17.0.1:6382,172.17.0.1:6383,172.17.0.1:6384
redis.store.nodes=172.17.0.1:6379,172.17.0.1:6380,172.17.0.1:6381,172.17.0.1:6382,172.17.0.1:6383,172.17.0.1:6384
Step 6: modify the current configuration if needed
---Si se quiere modificar alguna otra propiedad, este es el momento.
Step 7: install current version
*install.sh (version nueva)
...