Continuous Integration (CI) is a development practice where members of a team integrate their work frequently, each integration being verified by an automated build to detect integration errors as quickly as possible.
Continuous Deployment (CD) is a practice where the code changes that passed automated testing can be rapidly and safely deployed to production.
Build automation is a best practice used during the software development life cycle to compile and package source code with an automation build script.
For example, Talend users can export the sources of a Job they created in the Studio as a zip file using Maven and they can re-use this generated archive file in Talend Management Console or Talend Administration Center to schedule the next executions of this Job.
Version control and Source Code Management (SCM) allow you to manage and track the changes made to the software by assigning revisions to these changes. Talend achieves this thanks to its shared Repository and branching system based on Git. For example, Talend users can use the Repository that is shared between the Studio and other applications, as well as its branching system to version changes.
To summarize, SDLC aims at designing a regular and continuous build and deployment followed by automated end-to-end testing to verify the integrity of the current code base. These requirements also apply to the development of the software new features.