...
FLEXDEPLOY-8.0.0.0 is affected by FLEXDEPLOY-11985 - When some customers upgrade to 8.0.0.0, they may hit the error:
Error deploying web application directory [/u01/flexdeploy/apache-tomcat-flexdeploy/webapps/flexdeploy] java.lang.IllegalStateException: Error starting child ... Caused by: java.lang.NoClassDefFoundError: oracle/i18n/util/LocaleMapper. If you hit this, see Solution for Caused by: java.lang.NoClassDefFoundError: oracle/i18n/util/LocaleMapper This solution is automatically implemented in 8.0.0.1 and future versions.FLEXDEPLOY 7.0.0.0 to 7.0.0.5 and 8.0.0.0 are affected by FLEXDEPLOY-12078. These versions do not properly purge as much data as they should. The artifact repository and database could be larger than expected. Upgrading to 7.0.0.6+ or 8.0.0.1+ is recommended to allow the appropriate data to be deleted.
FLEXDEPLOY-8.0.0.4 is affected by FLEXDEPLOY-12644. Where the Release Dashboard and Edit Pipeline screens display an "Internal Error - Invalid ext class" message. This error occurs in cases where pipeline versions contain Manual Steps. This is resolved in 8.0.0.5. If you are upgrading to 8.0, use 8.0.0.5+.
FLEXDEPLOY-8.0.0.0-8.0.0.4 are affected by FLEXDEPLOY-12654 - Endpoint Execution Choice does not default properly when converting a workflow xml where Endpoint Execution was never chosen before migrating to the new 8.0 format. This is resolved in 8.0.0.5. If you are upgrading to 8.0, use 8.0.0.5+.
FLEXDEPLOY-12997 - When customers upgrade to the Oracle FSM October release, older builds no longer deploy successfully, giving plugin - builds and deployments between different FSM releases fail with a 400 error on import. To resolve this issue, upgrade to plugin version 8.0.0.7.56.
...