CI/CD
Also known as: Continuous Integration, Continuous Delivery, Continuous Deployment
Following adds this technology to your private workspace so related learning is easier to organise and revisit.
What is CI/CD?
Continuous integration and continuous delivery are practices for automatically validating, packaging and releasing software changes. This profile connects the concept to KBY's practical engineering guidance.
CI gives developers rapid feedback by building and testing each change, while delivery pipelines promote immutable artefacts through controlled environments. Effective pipelines include provenance, approvals, secrets boundaries, rollback and observable deployment outcomes.
Move software changes from source control to production repeatably and safely.
- Automated software testing
- Continuous deployment to production
- Infrastructure as code validation
Explore related technologies
Related technologies
3 resources for CI/CD
Browse by purpose, from definitions and learning through operations, diagnostics and controlled recovery.
Learn and operate with CI/CD
Ordered as a reader progression -- from core definitions through to operational reference -- using only the content already connected in the technology registry.
Systems Engineering(2)
Learn the architecture, concepts and engineering context.
- Immutable CI/CD Backups via S3 Object LockA technical guide to building an immutable backup architecture for CI/CD artifact registries using S3 Object Lock, Compliance mode, and cross-account replication. Open
- Cache Invalidation Strategies for High-Throughput CI/CD PipelinesStopping CI/CD cache invalidation storms with content-addressable keys, distributed locks, and tiered caching across Kubernetes runner fleets. Open
Daily Triage(1)
Practise diagnosis through bounded engineering scenarios.