Deployment of a new version of a managed application
- Solution
- new set of states for an Application that are independent from the current states: UP_TO_DATE, WAITING_FOR_UPDATE (version is waiting to be installed), UPDATING, ERROR (blocking the application?). We call it the update state.
- push a new version on a Cameo server. It is a request when processed:
- application becomes WAITING_FOR_UPDATE immediately
- the new version data is saved locally and replaces the previous new version if it is not installed yet
- the server installs it when the application is stopped (option: stop the application immediately)
- the application has the state UPDATING (new state in the current list)
- the config file is modified after each installation (to memorize the version number)
- the server shall not be brutally stopped
- enable to stop nicely the server
- default installation: copy file (jar) to install_directory, untar a tar to install_directory
- or an installation script
- command line: cmo app1 update app1.jar 1.2.3
- monitoring notifications:
- the Cameo server publishes a new status when the version is installed
- status VERSION value
- version in the application info
- class This can access version
To upload designs, you'll need to enable LFS. More information