---
title: "Continuous Pipeline Deployment"
canonical: "https://docs.vaultspeed.com/space/VPD/3011248154/Continuous%20Pipeline%20Deployment"
format: markdown
---
VaultSpeed also assists you in deploying your generated code to your database or GIT repositories.  Or you can even deploy to whatever you want if you use the custom script option.

# Automatic Deployments

By default, you can use a JDBC connection to automatically deploy the code to a target database.  More info here: [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3013804059](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3013804059) 

Or you can also use the option to deploy directly to a GIT repository.  More info here: [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3013148700](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3013148700) 

You can also write your own custom script to do the deployment.  More info here: [https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3013771287](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3013771287) 

# Manual Deployment

- **DDL: **To execute the generated DDL, unzip the latest "<id>_DDL.zip" and execute the SQL code in the files, the files should be executed in alphabetical order (order number in the filename).
- **SQL ETL: **To deploy the generated ETL, unzip the latest "<id>_GENERATE_ETL.zip" and execute the SQL code in the files, the files should be executed in alphabetical order (order number in the filename).  
If the target does not support SQL procedures then the generated code for the mappings does not need to be deployed.  Instead, the code in the SQL files needs to be executed as described in [Loading procedures](https://vaultspeed.atlassian.net/wiki/spaces/VPD/pages/3013804066). Note that the code for the views still needs to be deployed.
- **Groovy ETL: **To deploy the generated ETL, unzip the latest "<id>_GENERATE_ETL.zip" and execute the groovy scripts.
- **Talend ETL: **To deploy the generated ETL, unzip the latest "<id>_GENERATE_ETL.zip" and execute the following shell script (fill in where needed).

<details>
<summary>MacOS Shell Script</summary>

```shell
adminUrl=""
remoteLogin=""
remotePassword=""

branch=""
technicalName=""
projectLogin=""
projectPassword=""

jobscriptFolder="/Users/name/agent/generated_files/81_GENERATE_ETL/" #must end with slash
talendScriptPath="/Users/name/Documents/Talend-Studio-20161216_1026-V6.3.1/createJobs_Talend.sh"
workspacePath="/Users/name/Documents/workspace/"

echo "initRemote $adminUrl -ul $remoteLogin -up $remotePassword
logonProject -pn $technicalName -ul $projectLogin -up $projectPassword -br $branch" > $talendScriptPath

for file in "$jobscriptFolder"* do
    f2=${file##*/}
    echo "createJob ${f2%.*} -sf $file -o" >> $talendScriptPath
done

./Talend-Studio-macosx-cocoa.app/Contents/MacOS/Talend-Studio-macosx-cocoa -nosplash -application org.talend.commandline.CommandLine -data $workspacePath scriptFile $talendScriptPath
```
</details>