How Does UrbanCode Deploy Handle Rollbacks?
UrbanCode Deploy comes with a Package Management System (PKS). The PKS knows how to install different types of packages: native packages such as MSIs and RPMs; JEE packages such as WARs and EARs; packages of database changes, or configuration changes; as well as flat file and many other types of packages. The support for each package type knows how to perform a rollback for that specific package type. For example, rolling back an EAR-file deployment requires redeploying the previous EAR file; a rollback of a flat-file deployment requires restoring all the original files that were deleted or changed and the removal of all files that were added by the deployment being rolled back. Rolling back database changes involves the execution of the user provided roll-back scripts.
Proven, Built-in Rollbacks
The roll-back strategies employed by UrbanCode Deploy are standard, and a good thing. UrbanCode Deploy uses are tried and true rollback strategies, providing their implementation without the need for developing and maintaining any scripts that implement rollback logic.