Continuous delivery occurs when developers frequently hand off new code to the quality assurance (QA) and operations teams for testing. It usually involves a production-like staging area, and there is often a time lag between a release and when it is reviewed, when changes are manually accepted and when the new code is released to production.
Within Talend, the goal of continuous delivery is to use Jenkins to automate the creation of Talend Administration Center tasks in the Job Conductor and deploy them on the Job Servers along with the option of configuring Triggers (Simple, Cron, File-based) for scheduling.
This article describe one of the ways to build this Jenkins Job to perform continuous delivery. However, based on the SDLC process defined within your project group, the design and implementation can differ.
For more information on MetaServlet, see Non-GUI operation in MetaServlet.
For more information on the options available under MetaServlet, see MetaServlet API commands.
For a recorded expert session on MetaServlet, see Talend Virtual CSM.
- The Continuous Integration (CI) implementation is already setup:
- The Jobs which are to be promoted to Testing and Pre-Production environments should be published to the Releases folder of the Nexus Artifacts Repository.
- The necessary software, such as Jenkins, Maven, Talend Administration Center, Git and Nexus are setup and running.
- The Jenkins Job is configured to build from Git, generate source files using CI-Builder, build the artifacts, test using Maven and publish to Nexus.