CI/CD (Continuous Integration / Continuous Delivery)
Definition
CI/CD (Continuous Integration / Continuous Delivery)
CI/CD combines Continuous Integration (automatically building and testing code on every commit) with Continuous Delivery (automatically preparing releases for deployment). Together, they form the backbone of modern software delivery.
In detail
Continuous Integration catches integration errors early by merging code changes into a shared repository multiple times per day. Each merge triggers an automated build and test run. Broken builds are fixed immediately.
Continuous Delivery extends this by automating the release process. Every change that passes the test suite is a release candidate. Deployment to production can happen at any time with a single approval step or fully automatically (Continuous Deployment).
How Tallence helps
Tallence designs and builds automated CI/CD pipelines on AWS CodePipeline, GitHub Actions, or GitLab CI.
Learn more about CI/CD implementationRelated terms
DevOps
An engineering practice that aligns development and operations teams around shared goals, automated pipelines, and a culture of continuous delivery.
Test Automation
Using specialised tools and frameworks to validate software automatically, catching regressions in every pipeline stage before they reach production.
Infrastructure as Code (IaC)
Managing and provisioning cloud infrastructure through machine-readable configuration files rather than manual console operations.
Explore more terms
All glossary terms→FinOps
An operating framework that connects technology, finance, and business teams to manage cloud spending with accountability and transparency.
Site Reliability Engineering (SRE)
An engineering discipline that applies software practices to IT operations, using SLOs and error budgets to balance reliability with delivery speed.
Hybrid Cloud
A composition of two or more cloud environments (private, community, or public) connected by technology that enables data and application portability.
Private Cloud
A dedicated IT environment used exclusively by one organisation, providing maximum control over data, network, and configuration.
Microservices
An architecture pattern where applications are decomposed into independently deployable services, each owning its domain, data, and deployment lifecycle.
Cloud-Native Development
Building applications designed for the cloud from the ground up, using containers, Kubernetes, serverless functions, and declarative infrastructure.