Configure the pipeline script provided by Talend to generate the project items according to the Maven phase you want to achieve and the repository you want to deploy your artifacts to.
Some parameters and credentials come from the secure files and variables you have stored in Azure DevOps. For more information about the Talend Maven parameters you can use when configuring your pipeline, see Talend custom Maven build options.
Set your own values for the environment variables defined at
the top of the script (project name, Job name/version/type, repository URL,
Tip: Look for the XXX references in the azure-pipeline.yml script provided by Talend as an example and replace them with values corresponding to your environment.
ExampleExample of a project named CICD, a Job named job_feature956 with a 0.1 version and a Docker image named cicd4talend:
variables: - group: Talend variables - name: project_name value: 'CICD' - name: jobs_to_build value: 'jobs/process/job_feature956_0.1' - name: docker_image_name value: 'cicd4talend'Warning: Syntax requirements:
- The value of the project_name variable must be in upper case otherwise it might cause build failure. If you used special characters in the project name or have any doubts on its final syntax you can check it in the parent pom.xml file of your project (talend.project.name variable in <project>/poms/pom.xml).
- The value of the jobs_to_build variable must be in lower case even if the original name of your Job/Route/Service contained upper case as all artifacts are in lower case in the .pom files required to launch the build.
- Do not add manually the "-SNAPSHOT" suffix to the version value. Snapshots and releases are decoupled from the version itself and must only be handled via the Studio preferences, see Changing the deployment version of each artifact at once.
Depending on where you want to publish artifacts, edit the artifact repository URL
stated in the artifact_url Azure variable you created
allows you to deploy artifacts into a Nexus maven-releases repository (for stable release artifacts in a Production environment).Note: If you want to deploy Jobs that use custom components, you need to use the -Dcomponents.* options as described in Talend custom Maven build options.
Edit the Talend Cloud
workspace and environment stated in the talend_ci_config
-Dservice.url=$(talend_cloud_url) -Dcloud.token=$(talend_cloud_token) -Dcloud.publisher.environment=PROD -context=Prod -Dcloud.publisher.workspace=ci-workspace -Dcloud.publisher.screenshot=true
allows you to deploy artifacts (with screenshots) into a Talend Cloud account inside a workspace named ci-workspace on a PROD environment while changing the context environment to Prod (using --context). This environment must have been defined previously in Talend Studio, however if you did not define any context parameters you can use --context_param to define them at build time.Note: The artifact published to Talend Cloud cannot be larger than 400MB.
To define the Maven phase you want to achieve: make sure the phase stated in the
goals line is the one you want to perform. The default goal
defined in the default script provided by Talend is
For more information on the Maven phases, see the Maven documentation.Tip: All build profiles (-Pdocker, -Pnexus, etc.) are listed in the parent pom.xml file of your project. Some default parameters, like the docker image name or the Open JDK name, can also be overwritten in this file.
- Save your changes and click Run to launch the execution of your build pipeline.