| Table of Contents |
|---|
...
In the CLI, the Deployment Packager is initiated by running deployPackager.groovy. The script has two main modes of action: packaging SQL scripts and parameters defined in a manifest file or packaging SQL scripts directly from an SCM repository.
The following sections show examples.
See also /wiki/spaces/DDOC59/pages/795837376CLI - Deployment Packager
SCM Mode Examples
- Check the SCM repository for new files to process. The "preview" flag runs through processing without actually doing anything. It is useful when you're getting the SCM tool configured with Datical.
hammer groovy deployPackager.groovy pipeline=pipeline_name scm=true [labels=<comma separated list>] preview
- Check the SCM repository for new files, process them, and update the repository pointer (in the deployPackager.properties file) to mark the files as processed.
hammer groovy deployPackager.groovy pipeline=pipeline_name scm=true [labels=<comma separated list>] hammer groovy
- Check the SCM repository for new files, process them, and update the repository pointer to mark the files as processed. The quiet option suppresses all informational messages.
hammer groovy deployPackager.groovy pipeline=pipeline_name scm=true [labels=<comma separated list>] quiet
- When employing FEATURE BASED MERGE MODE, run the script with a
dbdef=<dbdef_name>parameter that targets a specific database definition within a project. For more information on this mode see /wiki/spaces/DDOC59/pages/795771705SQL Code Branching & Merging (Advanced).
hammer groovy deployPackager.groovy dbdef=<dbdef_name> scm=true [labels=<comma separated list>]
- Example command that can be used at the command line or in a Jenkins job. Note that the value passed for
--projectKeyis actually the project name and not the project key from DMC.
hammer groovy deployPackager.groovy pipeline=pipeline_name scm=true --daticalServer=dmc_server_url --daticalUsername=user_name --projectKey=project_name
Manifest Mode Examples
- Process the SQL files listed in the manifest file. The "preview" flag runs through processing without actually processing SQL scripts. It is useful for validating the manifest file when getting your system configured.
hammer groovy deployPackager.groovy pipeline_name manifest=<file.json> [labels=<comma separated list>] preview
- Process the SQL files listed in the manifest file.
hammer groovy deployPackager.groovy pipeline_name manifest=<file.json> [labels=<comma separated list>]
- Process the SQL files listed in the manifest file. The quiet option suppresses all informational messages.
hammer groovy deployPackager.groovy_name manifest=<file.json> [labels=<comma separated list>] quiet
...