topic Re: Talend CI/CD Pipeline using github actions in Talend Studio

Talend CI/CD Pipeline using github actions

suhasini12345 — Fri, 15 Nov 2024 22:43:31 GMT

Can anyone let me know the steps and requirements for building a CI/CD pipeline using Github actions for Talend and how to do Using GitHub Action for Talend to Publish to Cloud.

Re: Talend CI/CD Pipeline using github actions

Anonymous — Thu, 21 Jul 2022 14:05:33 GMT

Hi @Suhasini Suri,

Can I ask if you are talking about the "Pipeline Designer" product or whether you are talking about a Talend job as a "pipeline". Sometimes the language used by different areas in the domain can cause some confusion. When we are talking about "pipelines" we are talking about Pipeline Designer.

Regards

Richard

Re: Talend CI/CD Pipeline using github actions

suhasini12345 — Fri, 22 Jul 2022 11:49:07 GMT

Actually we want to build a workflow using github actions CI/CD pipiline for talend

Below is the yaml file

- name: Talend Publish to Cloud Action

# You may pin to the exact commit or the version.

# uses: Talend-Marketing/publish-to-cloud@a777e106550e236524225d6981ebf7f13f46f0ac

uses: Talend-Marketing/publish-to-cloud@v1.0

with:

# Talend Cloud Project name (always uppercase in your git repository)

project:

# P2 repository URL

updatesite_path:

# Talend Cloud URL

service_url: # optional, default is https://tmc.us.cloud.talend.com/inventory/

# Publish accelerate option (default to true)

service_accelerate: # optional, default is true

# Talend Personal Access token (PAT) for Talend Cloud

cloud_token:

# Publish skip option (defaut to false)

cloud_publisher_skip: # optional, default is false

# Talend Personal Access token (PAT) for Talend Cloud

cloud_publisher_screenshot: # optional, default is true

# Updateflow option (default to true)

cloud_publisher_updateflow: # optional, default is true

# Talend Cloud environment

cloud_publisher_environment: # optional, default is <default>

# Talend Cloud workspace

cloud_publisher_workspace: # optional, default is Personal

# Nexus URL for Talend Maven plugins and shared custom libraries

nexus_url:

# Nexus username

nexus_username:

# Nexus password

nexus_password:

# Talend license path in your repository. Make sure to encrypt your license.

license_path: # optional, default is license.gpg

# Passphrase used to encrypt Talend license in your repository. Make sure to store the passphrase in a secret.

license_passphrase:

Can you let me know what are the above parameters and how to get them

Re: Talend CI/CD Pipeline using github actions

suhasini12345 — Mon, 25 Jul 2022 15:59:34 GMT

@Richard Hall

Do you have idea how to build a CI/CD pipeline using github actions for Talend?

Re: Talend CI/CD Pipeline using github actions

Anonymous — Wed, 27 Jul 2022 12:03:17 GMT

I think that this was posted on the wrong board. The Pipeline Designer board is for the Pipeline Designer product. People won't be expecting this sort of question there. I have moved this to a more appropriate board.

In regard to your question, have you seen this?

https://community.talend.com/s/article/A-Github-Action-for-Talend-CI-CD-EugOq

Re: Talend CI/CD Pipeline using github actions

suhasini12345 — Wed, 27 Jul 2022 12:48:59 GMT

Yes ,I have seen that ,but Im not understanding what are the parameters to be used to run the workflow yaml

name: Talend Jobs Publish to Cloud

on: [push]

jobs:

talend_publish_to_cloud:

runs-on: ubuntu-latest

name: An action to publish Talend jobs to Cloud

steps:

- name: 'Checkout Github Action'

uses: actions/checkout@master

- name: 'Publish to Talend Cloud'

uses: Talend/publish-to-cloud@v0.1

with:

args: -e -am -X

project: CIPROJECT

updatesite_path: http:///jenkins/userContent/

service_url: https://tmc.us.cloud.talend.com/inventory/

cloud_token: ${{ secrets.cloud_token }}

nexus_url: http:///nexus

nexus_username: ${{ secrets.nexus_username }}

nexus_password: ${{ secrets.nexus_password }}

license_path: license.gpg

license_passphrase: ${{ secrets.LARGE_SECRET_PASSPHRASE }}

what is updatesite_path?
What is nexus here why should we use that to run talend workflow