RapidDeploy 3.5 Deprecated Features

The old stuff we're removing from RapidDeploy..

Contact Us

The following 3.5 deprecated features will be removed in the RapidDeploy 4.0 release, either because they aren't used or supported anymore, or because they are making way for other improvements.

Deprecated Feature Notes
 Binary Installation job type and associated
Environment Installation panels.
Binary installation and Code Deploy jobs are merged together
and follow the Code Deploy methodology. 
Support for Binary Installation job type continues in RapidDeploy 3.5 until
the end of life of this product version. 
 
Internet Explorer support for IE9.  Support for IE9 is removed following release of IE10 and IE11
Support for IE9 continues in RapidDeploy 3.5 until the end of life
of this product version. 
 
 
Binary Tasks. Binary Tasks are moved to standard deployment tasks.
Binary InitialisationTask and FinalisationTask are removed.  
Support for Binary Installation job type continues in RapidDeploy 3.5 until
the end of life of this product version. 
 
JMX Inbound calls. Calling RapidDeploy viathe JMX API can be tricky to configure. The REST Web
Services API is now more advanced than the JMX one, is more flexible and is relatively simple to invoke. Therefore the JMX API for
inbound calls to RapidDeploy is being deprecated.
 Dictionary files for each environment (.dict) files removed and replaced with a single project dictionary.xml ​Each project will have just one dictionary file, which simplifies the project
structure and facilitates validation of dictionary values.
Project environment files (.env, .xpath, .props etc) for each
environment replaced by either values on the environment panel, stored in the existing domainxml file,  or on the orchestration task itself.
Simplification of project structure and moving environment values from 
project to environment panel. From RapidDeploy 4.0 the environment files are no longer supported.
sourceRelativeToArchiveRoot and targetRelativeToArchiveRoot parameters path specifications in tasks are removed from task specification in 4.0 (but can still be set manually for backwards compatibility). In 4.1 they will be removed entirely. Replaced with ${ARCHIVE_ROOT} in the path (available since 3.5), if the path is relative to the archive root. Tasks using sourceRelativeToArchiveRoot should set this to 'false' and move to using ${ARCHIVE_ROOT} instead.