Talend custom Maven build options
mvn \
-f <project name>/poms/pom.xml \
-am -pl <comma separated list of jobs modules> \
-Dgeneration.type=local
-Dlicense.path=<local path or url> \
-Dupdatesite.path=<local path or url> \
clean deploymvn -f C:/CI_CD/MYPROJECT/poms/pom.xml clean deploy -fn -e -pl jobs/process/priorTest_0.1 -am -Dlicense.path=C:/CI_CD/license -Dupdatesite.path=http://localhost:8080/P2/ -Dproject.distributionManagement.snapshotRepository.url=http://localhost:8081/repository/snapshots/ -Dproject.distributionManagement.snapshotRepository.id=snapshots -DaltDeploymentRepository=snapshots::default::http://localhost:8081/repository/snapshots/Talend-related Maven parameters
| Maven parameter | Value | |
|---|---|---|
| Talend CommandLine parameters | -Dupdatesite.path | URL address of your server where the P2 repository with Talend CommandLine can be downloaded and installed
at build time. This site also contains the Maven plugins and all the external
libraries necessary to build your pipelines. For an example of how to embed the P2
repository in your Tomcat application, see Before scheduling the execution of your artifacts. Example:
Information noteWarning: This parameter only applies to users who have the P2 update site
archive, which is provided by Talend.
|
| -DforceUpdate | (No value) Forces the installation of Talend CommandLine from the update site, even if a local installation is present. | |
| -Dpatch.path | Path to the patch you have installed or want to install
(Talend Studio p2 patch, manual patch, component patch, etc.). Example if you have
installed the patch
locally:
Example
of patch to
download:
If credentials are needed to access the remote patch location, use the -Dpatch.remote.user and -Dpatch.remote.password parameters. The patch.remote.password parameter can set a password encrypted by Maven. |
|
| -Dgeneration.type | Type local as the value to
generate the sources of your artifacts and Tests locally without having to keep the
Talend CommandLine up and running during the
build execution. Example:
The server generation type is deprecated. |
|
| -Dlicense.path | Path to the license of your Talend product. If the licence path value is a URL and credentials are needed to access it, use the -Dlicense.remote.user and -Dlicense.remote.password parameters. |
|
| -Dcommandline.skip | Type true as the value to
skip the source code generation of your artifacts. This parameter can only be used if
you have previously generated your artifacts using Talend CommandLine. Example:
|
|
| Artifact repository parameter | -DaltDeploymentRepository | When deploying to an artifact repository (Nexus, Artifactory), specifies an
alternative repository to which the project artifacts should be deployed. Format: id::layout::url Example:
|
| Docker parameters | -Ddocker.push.registry | Specifies the Docker registry where you want to share your image. |
| -Ddocker.push.username | Specifies the Docker user corresponding to the account that will log in to the
Docker registry. In the default script provided by Talend, the value corresponds to the ${env.Dusername} variable, that is the Docker user defined in the credentials stored in Jenkins. |
|
| -Ddocker.push.password | Specifies the Docker password corresponding to the account that will log in to
the Docker registry. In the default script provided by Talend, the value corresponds to the ${env.Dpassword} variable, that is the Docker password defined in the credentials stored in Jenkins. |
|
| -Dtalend.docker.name | Specifies the name of the Docker image that will be created. | |
| -Dtalend.project.branch | Specifies the tag and related tagged artifacts you want to
build. Example:
|
|
| -Xms -Xmx | JVM arguments that allow you to increase the memory available to Maven. | |