Cloud DevOps Service

Development

The Development environment shows the full Continuous Integration Stack, as it is in this environment that Talend artifacts are designed, built and tested. It is from the Development Environment that Artifacts are published to Talend Cloud.

Talend provides a Maven plugin called Cloud CI Publisher, that uses the P2 repository to build Talend Metadata extracted from Git (via a Git plugin) into binary artifacts that can be deployed to Talend Cloud ready for deployment and execution. For more information, see Cloud DevOps Service.

As Cloud CI Publisher is a Maven plugin, you can leverage the build tool of your choice. While you can install, configure and maintain a tool such as Jenkins on a bare server, modern approaches to CI/CD favour the use of IaaS or Cloud DevOps tooling. See Continuous Integration - Defined and Decoded for a deeper overview.

Other Environments

Outside of the Development Environment, the Cloud Devops only serves one purpose for SDLC - to call the Talend Cloud Promotion Pipelines API. This is why the complete set of SDLC components do not exist in the Test, Pre-Production and Production environments.