StartBeginner25 min read
1. How to use this roadmap
CI/CD Pipelines · 48 pages source format
CI/CD is how modern teams ship. This path uses GitHub Actions as the primary lab — concepts transfer to GitLab CI, Jenkins, CircleCI. Build a public pipeline portfolio repo.
What you'll learn
- 8–10 week pacing
- CI vs CD vs continuous deployment
- Portfolio definition
Study pace
1–1.5 hours daily. Pipelines are learned by breaking and fixing — expect red builds.
- Recommended: ~8–10 weeks
- Accelerated: ~5–6 weeks
- Slow: ~12 weeks
Do this now
Fork or create cicd-journey repo. Enable Actions if fork.
Clear?
Lab repo
Use a small Node, Python, or static site repo — something with install, test, build steps.
Do this now
Pick repo with at least npm test or pytest. README explains app purpose.
Clear?
Checkpoints
Gate 1: PR workflow. Gate 2: secrets + artifacts + environments. Gate 3: rollback + production gates.
Do this now
Read checkpoint chapters. Copy criteria to README.
Clear?