Deploying your project artifacts

For more information on the Maven phases, see the Maven documentation.
For examples of filters you can apply to the execution of your project items, see Filtering the execution of your project on selected artifacts.

Tip: All build profiles (-Pdocker, -Pnexus, etc.) are listed in the parent pom.xml file of your project.

Deploying to an artifact repository

Configure the pipeline script provided by Talend to deploy your artifacts to the artifact repository of your choice.

From the Jenkins home page, select your pipeline to edit its configuration.
To define the artifact repository in which you want to deploy the project artifacts, edit the -DaltReleaseDeploymentRepository and -DaltSnapshotDeploymentRepository parameter values stated in the 'Talend On prem' stage.
Example to deploy artifacts into a Nexus snapshots repository (for projects under development and artifacts with a -SNAPSHOT version):
```
-DaltReleaseDeploymentRepository=releases::default::http://localhost:8081/repository/snapshots/
```
You need to specify your own artifact repository URL and there should not be any line breaks between the parameter and its value.
Save your changes.

Deploying to Talend Cloud

Configure the pipeline script provided by Talend to deploy your artifacts to Talend Management Console.

From the Jenkins home page, select your pipeline to edit its configuration.
To define the Talend Management Console publication details, edit the -Dservice.url, -Dcloud.token, -Dcloud.publisher.screenshot, -Dcloud.publisher.environment and -Dcloud.publisher.workspace parameter values stated in the 'Talend Cloud' stage.
Example to deploy artifacts (with screenshots) into a Talend Cloud account inside a workspace named ci-workspace on a prod environment:
```
-Dservice.url=https://tmc.eu.cloud.talend.com/inventory
-Dcloud.token=XXX1234TalendCloudToken1234XXX
-Dcloud.publisher.screenshot=true 
-Dcloud.publisher.environment=prod
-Dcloud.publisher.workspace=ci-workspace
```
You need to specify your own Talend Cloud environment and workspace.
Save your changes.

Deploying to Docker

Configure the pipeline script provided by Talend to deploy your artifacts to Docker.

From the Jenkins home page, select your pipeline to edit its configuration.
To define the Docker registry in which you want to deploy the project artifacts, edit the -Djkube.docker.push.registry, -Djkube.docker.username, -Djkube.docker.password parameter values stated in the 'Talend with Docker' stage.
Example to deploy artifacts as the Docker image you have previously defined in the Docker registry of your choice:
```
-Djkube.docker.push.registry=talenddockerregistry 
-Djkube.docker.username=talenduser 
-Djkube.docker.password=Talenddock3rpassw0rd
```
Save your changes.

Multiple deployments at once

Configure the pipeline script provided by Talend to deploy your artifacts to multiple places (artifact repository, Talend Cloud, Docker).

From the Jenkins home page, select your pipeline to edit its configuration.
In the stage you want to edit, define the Maven phase you want to achieve, and make sure the profiles stated correspond to where you want to deploy. The list of profiles should be comma-separated.
Example:
```
mvn deploy -Pdocker,cloud-publisher 
```

To define the repositories and environments in which you want to deploy the project artifacts, edit the parameter values stated in the mavenOpts parameter.

Example to deploy artifacts both into a Nexus snapshots repository and a Talend Cloud account:

-DaltDeploymentRepository=maven-snapshots::default::http://localhost:8081/repository/maven-snapshots/
-Dservice.url=https://tmc.eu.cloud.talend.com/inventory
-Dcloud.token=XXX1234TalendCloudToken1234XXX
-Dcloud.publisher.screenshot=true 
-Dcloud.publisher.environment=prod
-Dcloud.publisher.workspace=ci-workspace

Save your changes.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here