Page Comparison

...

1. Checkout the SQL code from the appropriate branch 
2. Checkout the DaticalDB project from the main branch
3. Run the deployer through the Command Line Interface (CLI) "hammer groovy deployPackager.groovy", this will includes:
   Image RemovedImage Added
4. Create an artifact ( comprised of the DaticalDB project directory)
5. After the artifact has been created, the process will be the same in each environment:
   1. download the artifact
   2. run the CLI to do a forecast
   3. run the CLI to execute the deployment itself

...

The file structure is typically as follow:

Image RemovedImage Added

where:

• portal_sql is the name of your repository, 
• sql_code is the name of the directory where the packager will look for new/modified .sql files to package, this directory is reference in the deployPackager.properties in your DaticalDB project
• the sub-directories represent the different kinds of SQL scripts to package. The process order for a commit is the following: ddl, sqlplus, sql, function, packagebody, package, procedure and finally data_dml. 

...

That step should look like:

Image RemovedImage Added

DaticalDB project repo

...

That step should look like:

Image RemovedImage Added

Build Triggers

...

Check "Delete workspace before build starts", repo is usually small so the cost of cloning it the whole project is negligible compare t to the benefit of a clean environment

Image RemovedImage Added

Build

This is where the real work is done for the deployer

...