Liquibase Enterprise was formerly known as Datical DB.
SCM Requirements and Features
- Former user (Deleted)
- Amber Williams
- Former user (Deleted)
- Anonymous
The Datical Project must have its own repository.
If the Datical Project is in a repository that contains other work, automatic commits run by Datical may commit other pending work.
SCM Solution | SCM Versions |
Git | 1.8.2-1.9.x, 2.x. Note: requires the Git command line client be installed and in the system path for all servers where Deploy Packager will run (example: git.exe). |
Git
Datical DB supports SSH, HTTP and HTTPS protocols with Git.
SCM Environment Variables (Git only)
Use environment variables to store credentials for the Deployment Packager to use when accessing Git and Subversion repositories.
Environment Variable | Description |
SQL_SCM_USER | User name and password for the repository that manages the SQL code for the Deployment Packager. |
DDB_SCM_USER | User name and password for the repository that manages the Datical project for the Deployment Packager. |
Environment Variable Usage & Deployment Packager Behavior
Deployment Packager is only available with Liquibase Enterprise product
- The environment variables must be set before you start the Deployment Packager.
- Specify both the username and password.
- Deployment Packager checks the environment variables before it attempts to connect to the SCM.
- If the SCM user and password variables are set, Deployment Packager uses them to connect.
- If the SCM user and password variables are NOT set, the Packager attempts to connect without using a username or password. This is the legacy connection method, which required that you use persistent external authentication methods before running Deployment Packager.
- If only one of the variables is set. the Deployment Packager halts and reports an error.
Copyright © Liquibase 2012-2022 - Proprietary and Confidential