CI/CD
CI/CD Foundations for Shipping Teams
420,000 KRW list tuition
Walk through repository layout, branch protections, and progressive delivery hooks using the same templates our mentors use in production reviews. Each week ends with a merge request your peers critique.
What you work through
- Branch policy pack with annotated examples
- Reusable workflow library for build and scan stages
- Promotion map covering dev, staging, and controlled prod
- Failure triage worksheet aligned with incident retros
- Secret rotation checklist scoped to CI runners
- Smoke test harness wired to ephemeral environments
Outcomes
- Ship a green pipeline that enforces tests before merge
- Document rollback ownership for two critical services
- Present a delivery risk brief your team can reuse
Mentor
Jonah Reeves
Former delivery lead for distributed retail stacks; focuses on humane defaults in automation.
FAQ
What tooling must I install before day one?
You receive a pinned tool matrix (CLI versions, editor plugins, VPN steps). Unsupported legacy OS releases are not included; you need a 64-bit system with admin rights for container runtimes.
How quickly are mentor reviews returned?
We target two business days for written feedback on deployment artifacts. Live sessions are scheduled in the cohort calendar; same-day turnaround is not promised.
Can my employer sponsor a private cohort?
Yes—volume packages include shared activity logs and a dedicated Slack bridge. Pricing follows the published tier sheet; custom SLAs require a separate statement of work.
Reviews
The canary module references the same Helm hooks we ship internally, so I could paste snippets without renaming everything.
Mentor called out my skipped readiness probe before it bit staging. Still wish the Terraform section had one more multi-env example.