CI/CD
Pipeline Foundations with GitLab CI
Wire up repeatable build and deploy stages with guarded promotions, cache hygiene, and artifact hygiene for platform teams.
- Duration
- 6 weeks
- Format
- Cohort lab nights (KST evening)
- Skill focus
- Intermediate
- Project intensity
- High
420,000 KRW
Informational tuition reference — no checkout on this static site.
Program narrative
This track focuses on turning a scattered script folder into a maintainable pipeline library. You will wire runners, isolate secrets, and practice rollback drills on a shared lab cluster. Mentors annotate your YAML with concrete edits so you leave with a pattern you can reuse on the next service.
Included focus areas
- • Runner sizing and queue tuning on shared infrastructure
- • Cache and artifact policies that keep builds fast
- • Promotion gates with manual approvals for production paths
- • Blue-green style deploy hooks without touching vendor dashboards
- • Structured logging that maps to on-call playbooks
- • Quality gates that block merges on flaky integration suites
- • Post-deploy smoke checks wired as first-class stages
Outcomes you can show
- Ship a two-environment pipeline with audited promotions
- Publish a reusable template library for sibling teams
- Document rollback steps that match the automation you built
Mentor of record
Hana Sato
Former platform lead for a mid-sized SaaS shop; now coaches teams on boring, reliable delivery.
Participant notes
The module on cache discipline finally stopped our mystery rebuilds. Still tightening secrets rotation, but the skeleton is solid.
Mentor comments on my promotion stages were blunt in a good way. I rewrote two jobs and cut average pipeline time noticeably.
Straight answers
No. You start in a shared lab tenant. Bring your own cluster only if you want parity homework reviewed.