Datical DB

Same Datical DB Version for All Users Working on a Release Pipeline

For any given release pipeline, all users that deploy changes to the pipeline should use the same version of Liquibase Enterprise/Datical DB. This requirement applies to all users:

• Individual Users - Users have Datical DB installed on their system. They use the GUI client or CLI to perform operations (package, deploy, status, rollback).

• Automation - An automation solution (like Jenkins) uses a Datical DB installation. The automation system runs Datical DB CLI commands to perform operations (package, deploy, status, rollback).

Same Database Version for All Databases in a Release Pipeline

It is best practice to have all dbDef steps in a release pipeline running the same version of the database platform. The version of the database should be consistent to provide a consistent experience when the same changes are deployed to each dbDef step in the pipeline.

...

DMC

Datical DB 7.x and DMC (Deployment Monitoring Console) Version Matching

DMC (Deployment Monitoring Console) 7.x versions typically need to match your Liquibase Enterprise/Datical DB 7.x version. There are a few exceptions for versions where there was a Liquibase Enterprise/Datical DB release but no correlating release for DMC. Please see the “Datical DB and Deployment Monitoring Console Compatability Matrix” here: https://dmc.datical.com/release-notes/release-notes-home.htm

Datical DB 5.x/6.x and Datical Service Version Matching

Datical Service 5.x/6.x includes an optional internal installation of Datical DB that is run by an internal Jenkins client. If you use Datical Service and also use the internal Jenkins Client option, you need to use the same version of Datical DB and Datical Service. However, if you do NOT use the Internal Jenkins Client you can run Datical DB 6.17 with Datical Service versions 5.8 to 6.17. Datical Service versions 5.x/6.x have been deprecated.

...