You configured the manifest, you can now execute the pipeline on your
sandbox.
Procedure
Click the Pipeline tab. This tab displays all the CI/CD
steps generated by Talend Cloud Migration Platform based on the selected target. The cloud-deployer Maven plugin is used for
this step.
Available step types:
Environment: A shell script
(.cmd or .sh) is executed
to display information about the current CI/CD environment, including
the version of the installed CommandLine and the versions of the tools
such as Java, Git, Maven, etc…
Git Clone: A shell script is executed to clone
the corresponding source Git repository.
Workspace copy: If the source of the Talend project is a folder, a script is executed to copy it into the current
Talend CommandLine workspace.
CVE Report Generation: A Maven shell script is
executed to generate the CVE report from Talend CommandLine.
CVE Report: A graphical representation is
generated from the generated CSV CVE report.
Generate Poms: A Maven shell script is executed
to generate the project Poms. The same script is executed to execute a
project upgrade.
Project Upgrade Report: A graphical
representation is generated from the generated CSV Upgrade report.
Package Artifacts: A Maven shell script is
executed to generate the selected assets (Jobs, Routes) artifacts.
Publish to Artifact Repository: A Maven shell
script is executed to publish the generated artifact to the selected
Artifact Repository.
Publish & Deploy to Cloud: A Maven shell
script is executed to publish the generated artifact to Talend Cloud and create the associated executions tasks.
Click Run to start the pipeline and execute all the
generated steps. A successful execution will have a green check mark for each
step and an execution time.
CVE Report step: The CVE Report will load the
.csv file generated by Talend CommandLine and process it to enhance the display with additional capabilities
such as the different groupBy fields and weblinks to the CVE tickets.
The original .csv file can also be directly
downloaded from the button on the right.
Package Artifact step: A successful Maven script
output shows a summary of all the generated assets artifacts.
Publish & Deploy to Cloud step: A successful
Maven script output shows a summary of all the generated assets
artifacts.
In addition to the Maven output, the cloud-deployer Maven plugin
generates an execution report with information about the Talend Cloud published artifact and created execution task. For example:
---------------
- Started : 2023-12-15 at 14:14:23
---------------
- PROJECT
- Name : PROJECT_721
- Branch : master
- Commit
- Id : 57d96b8de6fc0eff3689d14e560b1f0f442d5b41
- Date : 2023-07-08T04:10:55+02:00
- Author : gandalf.thegrey@middle-earth.talend.com
- MODULE
- Type : process
- Name : job1
- Version : 0.2
- folder :
- TALEND CLOUD
- Domain: AWS_US
- Environment: redha-dev
- Id : 6207f129ce4cda223c78f732
- Workspace : test3
- Id : 63b6a8727e1af864dcfd87e0
- Artifact
- Name : job1
- Id : 651cc33ba572351e47a557d2
- Version : 0.1.31.20231612071428
- Url : https://app.us.cloud.talend.com/manage-artifacts/6207f129ce4cda223c78f732/workspace/63b6a8727e1af864dcfd87e0/detail/job/651cc33ba572351e47a557d2
- Task
- Name : task_project_721_job1
- Id : 6566918d7626287ce7bedd81
- Version : 3.3
- Engine : cluster-asg (REMOTE_ENGINE_CLUSTER)
- Url : https://app.us.cloud.talend.com/tasks-and-plans-administration/6207f129ce4cda223c78f732/63b6a8727e1af864dcfd87e0/tasks/job/6566918d7626287ce7bedd81/detail
---------------
- Ended : 2023-12-15 at 14:14:32
---------------
- Durations
- Publish : 00:03.787 min
- Deploy : 00:03.718 min
- Total : 00:09.077 min
Results
On Talend Management Console, the
Management page displays the newly created tasks.
In the task details, you can find the corresponding CI/CD manifest configuration
options:
Task name generated based on the task name template
Selected environment and workspace
Task description generated based on the description template
The selected Runtime
The associated asset artifact
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!