Pathwise

Manuals / CI/CD Pipelines / Guide 1

Start · beginner · ~25 min · Guide 1 of 12

How to use this roadmap

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.

Path progress
3%

Step 1 of 3

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
Study paceDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Study pacedrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Fork or create cicd-journey repo. Enable Actions if fork.

Was this step clear?
Chapter learning outcomes
  • 8–10 week pacing
  • CI vs CD vs continuous deployment
  • Portfolio definition

Clear these before you leave

Side quest

Day zero

README with pipeline goals and timeline.