1. Foundations of CI/CD
Continuous Integration (CI) is a development practice where engineers frequently merge code changes into a shared repository — often multiple times per day. Each merge triggers an...
Read full chapter →The essential Cicd Pipelines cheat sheet: 7 concise chapters you can read in minutes, distilled from the full deck. When you're ready, drill the flashcards or test yourself under exam conditions.
Continuous Integration (CI) is a development practice where engineers frequently merge code changes into a shared repository — often multiple times per day. Each merge triggers an...
Read full chapter →GitHub Actions is a CI/CD platform built directly into GitHub, where every push, pull request, or scheduled event can trigger an automated workflow defined in YAML under `.github/w...
Read full chapter →Jenkins pioneered the idea of pipeline as code with the Jenkinsfile, a text file checked into the repository root that defines the build in Groovy. Declarative pipelines are the re...
Read full chapter →Build artifacts are the output files produced by a build stage — compiled binaries, Docker images, test reports, coverage reports, or any other deliverable. They flow between stage...
Read full chapter →Testing is the engine of CI's feedback loop. The test pyramid says you should have many unit tests at the base, fewer integration tests in the middle, and a small number of end-to-...
Read full chapter →The deploy stage is where built artifacts become running software, and choosing a strategy shapes both safety and velocity. A recreate deployment simply shuts down the old version...
Read full chapter →Modern CI/CD pipelines must defend against attacks on the software supply chain. A Software Bill of Materials (SBOM) is a machine-readable list of every component in an artifact —...
Read full chapter →Done reading?
Test yourself with the Cicd Pipelines practice exam — timed questions, instant score, full review of wrong answers. Free.
🎯 Take the Practice Exam →