Running the Azure DevOps pipeline - 8.0

Talend Software Development Life Cycle Best Practices Guide

Version
8.0
Language
English
Product
Talend Big Data
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Module
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend JobServer
Talend Studio
Content
Administration and Monitoring
Deployment
Design and Development
You have the possibility to run the build manually or trigger it based on changes made to your project. By default, there is no build trigger in the script provided by Talend but you can change the trigger parameter value to master if you want to automatically trigger a build whenever a commit is made on the master branch of your project for example.

Procedure

  1. Go to Pipelines > Builds.
  2. Either click Queue to queue another build with the same parameters or Edit to update the azure-pipelines.yml and run a build to take these changes into account.

Results

Once your pipeline has been successfully executed, you can see the detail of each step.

The pipeline is launched and your project is being processed according to the Maven phases that have been defined in your script. The best practice is to use the deploy phase in order to generate the source code, compile it, test it, package it and then deploy the packages.

You can see their results displayed:

  • in the Azure DevOps pipeline detailed view: the detail of your results can be found in the logs that you can display by clicking the Maven step.
    Example where you can see the successful execution of the test named test_feature903:
  • in Talend Cloud Management Console: example of Job and Route artifacts with version 0.1.0 deployed in the ci-workspace workspace of the dev-ci environment:

    The option to display Git information (author, commit ID, commit date) in Talend Cloud Management Console when publishing artifacts using Continuous Integration builds is available from version 8.0.1 onwards (available from R2022-01).

  • in your Nexus web application or Artifactory: example of Job and Route artifacts with version 0.1.0 deployed in the maven-releases repository with an org.talend.ci Group ID:
  • in your Docker registry: example of Job and Route artifacts with version 0.1 pushed in a Docker image called ci_image of a Docker registry called ci_repo: