Why this matters
- This topic directly affects how reliably BookStore reaches production — gitlab ci stages mirror bookstore environments with runner tags and tracked deployments..
- Interviewers connect hands-on commands and manifests to real delivery stories, not buzzwords.
- Later modules assume you can explain both the why and the concrete file or command involved.
- Platform maturity shows up when teams automate this instead of relying on tribal knowledge.
SourceGit push / PR
Buildmvn package
TestUnit + integration
PackageDocker image
PublishPush to registry
DeployStaging → Prod
Stages and runners
Tags and executors: BookStore engineers treat this as part of the standard path from laptop to gitlab ci pipelines readiness. Document decisions in the team runbook so on-call knows which knobs exist.
Key ideas
- Stages and runners — primary idea for gitlab-ci-pipelines
- BookStore context — catalog API, checkout, and inventory services share the same pattern
- Automation — prefer pipeline jobs over manual SSH steps
- Verification — staging must prove the change before prod traffic
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 2 sections
- Environments
- Production checklist
Test yourself
Answer these before moving on — recall is what makes it stick.