Library › Book 16 › The CI/CD Landscape
The CI/CD Landscape
1.1What CI/CD Actually MeansContinuous Integration (CI) is the practice of merging code changes into a shared branch frequently -- at least once a day -- and…1.2The Pipeline as a Safety NetThink of your pipeline as a series of increasingly rigorous checkpoints. A commit enters from one end and, if it survives every checkpoint…1.3The Big Four PlatformsAs of 2026, most teams use one of four CI/CD platforms. Each has its own configuration format and hosting model, but they all share the…1.4Shared Concepts Across All PlatformsRegardless of which platform you use, the following concepts work the same way. Understanding these makes switching platforms…1.5Choosing a PlatformFor most teams, the choice is simple: use what integrates with your source control. If your code is on GitHub, use GitHub Actions. If it is…1.6Career Translation- Evaluated and selected CI/CD platforms (GitHub Actions, GitLab CI, Jenkins, CircleCI) based on integration requirements, cost modeling…1.7Q&AInterview Depth CheckPrompt: Your team is migrating from a monolith on Jenkins to microservices on GitHub. The CTO wants everything moved in one sprint. How do…