# Deployment-related Maven parameters

These parameters allow you to deploy your artifacts to an artifact repository, to Talend Cloud or to Docker.

* To get the list of Cloud-related Maven parameters as inline help during build time, execute this command:
  ```
  mvn org.talend.ci:cloudpublisher-maven-plugin:<version>:help 
  -Ddetail=true 
  -s F:/<your_studio>/configuration/maven_user_settings.xml
  ```
* To get the list of Docker-related Maven parameters as inline help during build time, execute this command:
  ```
  mvn org.eclipse.jkube:kubernetes-maven-plugin:<version>:help 
  -Ddetail=true 
  -s F:/<your_studio>/configuration/maven_user_settings.xml 
  ```

Information noteTip: To deploy your artifacts to multiple places at the same time (artifact repository, Talend Cloud, Docker), enter comma-separated values like -Pnexus,cloud-publisher.

| Maven parameter | Value |  |
| --- | --- | --- |
| Artifact repository parameters | -Pnexus | (Activated by default unless a different profile is specified which<br>deactivates it)<br><br>Activates the plugin that allows you to publish to your<br>artifact repository (Artifactory, Nexus). |
| -DaltSnapshotDeploymentRepository and<br>-DaltReleaseDeploymentRepository<br><br>OR<br><br><br>-DaltDeploymentRepository | When deploying to an artifact repository, specifies an [alternative repository](https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html) to which the<br>project artifacts should be deployed.<br><br>Format: id::layout::url<br><br>Example<br>for projects with a snapshot<br>version:<br><br>```<br>-DaltSnapshotDeploymentRepository=snapshots::default::http://localhost:8081/repository/snapshots/<br>```<br><br>or<br><br>```<br>-DaltDeploymentRepository=snapshots::default::http://localhost:8081/repository/snapshots/<br>```<br><br>Example<br>for projects with a final<br>version:<br><br>```<br>-DaltReleaseDeploymentRepository=releases::default::http://localhost:8081/repository/releases/<br>```<br><br>or<br><br>```<br>-DaltDeploymentRepository=releases::default::http://localhost:8081/repository/releases/<br>``` |  |
| Talend Cloud parameters | -Pcloud-publisher | Activates the plugin that allows you to publish to Talend Cloud. |
| -Dservice.url | Specifies the Talend Cloud account in which the project artifacts should be deployed.<br><br>In the default<br>script provided by Talend, the value corresponds to the ${CLOUD\_URL} variable<br>that is defined at the beginning of the script. |  |
| -Dcloud.token | Specifies the access token generated for your Talend Cloud account. |  |
| -Dcloud.publisher.environment | Specifies the environment created in your Talend Cloud account in which the project artifacts should be deployed.<br><br>Example:<br><br>```<br>-Dcloud.publisher.environment=PROD<br>``` |  |
| -Dcloud.publisher.workspace | Specifies the workspace created in your Talend Cloud account in which the project artifacts should be deployed.<br><br>Example:<br><br>```<br>-Dcloud.publisher.workspace=CI_WORKSPACE<br>``` |  |
| (Optional)<br><br>-Dcloud.publisher.screenshot | Add this parameter with a true value if you want to<br>publish the capture of the artifact to be deployed in your Talend Cloud account.<br><br>```<br>-Dcloud.publisher.screenshot=true<br>``` |  |
| (Optional)<br><br>-Dcloud.publisher.updateFlow | Add this parameter with a true value if you want to<br>create or update the corresponding Talend Management Console task when publishing a new artifact version into Talend Cloud.<br><br>```<br>-Dcloud.publisher.updateFlow=true<br>``` |  |
| Docker parameters | -Pdocker | Activates the plugin that allows you to publish to a Docker<br>registry. |
| -Djkube.docker.push.registry | Specifies the Docker registry where you want to share your image. |  |
| -Djkube.docker.username | Specifies the Docker user corresponding to the account that will log in to<br>the Docker registry.<br><br>In the default script provided by Talend, the value corresponds to the ${env.Dusername}<br>variable, that is the Docker user defined in the credentials [Storing login credentials in Jenkins](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/storing-login-credentials-in-jenkins). |  |
| -Djkube.docker.password | Specifies the Docker password corresponding to the account that will log in<br>to the Docker registry.<br><br>In the default script provided by Talend, the value corresponds to the ${env.Dpassword}<br>variable, that is the Docker password defined in the credentials [Storing login credentials in Jenkins](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/storing-login-credentials-in-jenkins). |  |
| -Djkube.docker.host | Specifies the hostname corresponding to the account that will log in to the<br>Docker registry. |  |
| -Dtalend.docker.dockerfile | Specifies the path to a custom Dockerfile.<br><br>Example:<br><br>```<br>-Dtalend.docker.dockerfile=C:/Talend/DockerFile<br>```<br><br>For<br>more information on how to customize a Dockerfile in Talend Studio, see [the Studio documentation](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/customizing-the-dockerfile-settings). For more<br>information about Dockerfiles, see [the Docker documentation](https://docs.docker.com/reference/dockerfile/). |  |

### In this section

* [Build failed when deploying to Talend Cloud on Java 17 - Workaround](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/build-failed-when-deploying-to-cloud-on-java17-workaround?id=22)