In Azure DevOps you can add your custom Maven files as well as your Talend product license or local patches as Secure Files and then use these files in the CI/CD pipelines.
Note: Storing Talend CI
Builder 8.0.4 or higher in Azure DevOps is optional. Starting from Talend CI
Builder 8.0.4, it is available in the
official Talend
repository, which is referenced in the maven_settings.xml
file available from the Downloads tab of this page.
Before you begin
- Retrieve these files from the Downloads tab of this page:
- maven_settings.xml
- sample_pom.xml
- Retrieve the CI Builder plugin archive, either from your license email, or from the Continuous Integration (CI) for cloud section of the Downloads page of your Talend Cloud account.
- Adapt the maven_settings.xml file to your environment by
replacing the parameter values (Nexus or Artifactory URLs, host names, ports,
credentials, etc.) and save your changes.Tip: Look for the XXX references in the file provided as an example and replace them with values corresponding to your environment. This example file is adapted for Nexus. If you are using another artifact repository like Artifactory, you need to adapt this example to your repository URLs.
Procedure
- On the page, go to the Secure Files tab.
- Click the plus sign to upload the maven_settings.xml.
- Once uploaded, click the uploaded file, select Pipeline permissions and make sure the Azure pipeline you create can use this variable group.
- Click the plus sign to upload your license file.
- Once uploaded, click the uploaded file, select Pipeline permissions and make sure the Azure pipeline you create can use this variable group.
- Click the plus sign to upload the Talend-CI-Builder-Maven-Plugin-20211109_1610-V8.0.x.zip CI plugin that you downloaded from your Talend Cloud account.
- Once uploaded, click the uploaded file, select Pipeline permissions and make sure the Azure pipeline you create can use this variable group.
- Click the plus sign to upload the sample_pom.xml file.
- Once uploaded, click the uploaded file select Pipeline permissions and make sure the Azure pipeline you create can use this variable group.