CI/CD
GitLab CI Blueprints for Multi-Stage Pipelines
You wire runners, cache layers, and promotion gates while mentors annotate every merge request. The arc moves from a single service to coordinated environments with manual approvals that still feel fast. Expect annotated YAML diffs nightly and a capstone that mirrors a brownfield repo split across two teams.
Format: Cohort + async reviews · Timeline: 6 weeks · 42h guided
List price: BRL 1.890 (informational, no checkout on this site)
Helena Prado
Former release train conductor for a logistics API mesh; now coaches YAML ergonomics.
Module map
- Runner topology maps for mixed shell and container executors
- Cache discipline workbook with measured cold vs warm builds
- Child pipeline choreography for contract tests before packaging
- Protected variable rotation lab with sealed context files
- Release evidence bundle template aligned to stakeholder sign-off
- Failure injection drills for flaky network segments
- Post-deploy smoke harness wired through review apps
Outcomes we expect to see
Ship a three-environment promotion map with explicit rollback switches
Document operational handoffs so on-call can trace each artifact hash
Instrument pipeline duration guardrails with actionable thresholds
FAQ — includes hard truths
No. You bring your own runner namespace or use our sandbox for exercises only; production wiring stays in your accounts.
Mentor-reviewed quotes
The child pipeline week finally made our contract tests stop blocking packaging. Still wish the cache lab had one more ARM example.
Iago M. · Build engineer · Regional SaaS billing · 5/5 · survey
Mentor notes on my protected variable rotation were sharper than any internal wiki we had.
Priya · Recife · Google