| Table of Contents | ||||
|---|---|---|---|---|
|
...
Liquibase Enterprise
Same
...
Liquibase Enterprise 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 haveLiquibase Enterprise 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 Liquibase Enterprise installation. The automation system runs Datical DB Liquibase Enterprise CLI commands to perform operations (package, deploy, status, rollback).
...
| Info |
|---|
Each step in a project represents a stage in the release pipeline. A step in Liquibase Enterprise software is also known as a dbDef, a connection, a target, or an environment. |
DMC
...
Liquibase Enterprise 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 Liquibase Enterprise 7.x version. There are a few exceptions for versions where there was a Liquibase Enterprise/Datical DB Liquibase Enterprise release but no correlating release for DMC. Please see the “Datical DB “Liquibase Enterprise 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.