Can you please elaborate more on below
Release : 8.0.0
Component : CONTINUOUS DELIVERY DIRECTOR
Please find more details around the below mentioned queries
With CDD our approach is roll-forward and henceforth we don't have a rollback procedure. CDD product aligns to standard enterprise on premise guidelines, which has below recommendation
- The rollback procedure should include backup of the database before the upgrade and restore the database in case of failure ( post upgrade or during upgrade).
- As this is very specific to DB it's currently in scope of DBA to do respective backup and restore of respective DB's.
At current there is no retention-policy built in product. However, we may support some retention policy for offline database tables of CDD, but that will be an Enhancement request and we can discuss the requirements of the same and can include them as features in future releases. (Please refer to release notes of CDD release to validate if it's been delivered in future releases)
Setup of MSSQL server in High Availability (HA) is very specific to MSSQL and the customer Database Administrator(DBA) should plan and provision for same.
The JIRA tickets related to the artifacts of a release in CDD (Planned vs. Actual ) does not require MongoDB. MongoDB is required for the operation of the Intelligent Test Module(CDI) of CDD for running Maven Testing, Selenium Testing, Cucumber Testing, etc...
End user can see the status of the ALM work items based on commit messages - without using MongoDB