GitHub Actions pipeline to build/publish/deploy

[jeffpriz]

Hi, I am super new to Talend, and really trying to dig in to the DevOps CI/CD picture for Talend

I am trying to understand the Talend Cloud CI/CD story. Lots of the documentation on Talend CI/CD seems to talk about the CI Portion but lacks on the Deployment .. How do we push an Artifact from Dev --> Test --> Prod?

I found this GitHub actions action in and read the blog post about using it

Talend Publish to Cloud Action · Actions · GitHub Marketplace

But I am struggling to understand the flow for Talend CI/CD. I can execute a Maven script to build, execute unit tests, and publish the artifact (seems like choices are Nexus, Artifactory, or a Docker Registry), then I can use the above task to publish it to Talend Cloud? is that true? So do I have multiple stages in my pipeline that publish to Dev, then to Test, then to Prod? or how does that promotion work? Team is currently utilizing TMC to promote but they only "Publish" from Talend Studio once, so I guess I'm unsure what the right process flow for this is.

thanks for any and all help

[Anonymous]

Hello,

Could you please have a look at this online documentation about: TalendHelpCenter: Software Development Life Cycle to see if it is what you are looking for?

Best regards

Sabrina

[jeffpriz]

Sabrina,

thanks for the reply.

I have reviewed that documentation previously, and re-looked at it now. This is part of what my trouble is. This documentation talks about the importance and value of doing CD, but there are no examples on how Talend supports deployment automation.

Under the section on "Building and Deploying" I was looking for examples of deploying ... but the links and discussions there only focus on Continuous Integration. I am looking for similar examples on Deployments automation.

[jeffpriz]

The only note here on Deployment in that documentation is :

Deploying to QA and Production environments

In Talend Cloud, the only tool needed to pass artifacts from one environment to another is the Talend Cloud Public API.

In Talend Cloud, environments are self-contained spaces with the required resources (connections, engines, and so on) that allow the execution of Flows in isolation, with no impacts on other environments. Therefore, executions in the QA environment must not impact executions happening in the Production environment.

But no examples of how to leverage that API. Also finding documentation on the API so I can try to formulate something has been a challenge.

Also, back to my original link, if I leverage GitHub actions, how/where does that github action to publish an artifact fit in? The documentation around that action is limited