Learn GitLab from first push to production: projects, groups, CI/CD pipelines, variables, runners, and a Docker deploy with a manual approval gate.
It is a Friday evening at a Pune fintech. A developer zips the build folder, copies it to the production server by hand, and heads home.
A project is the basic unit in GitLab: one Git repository plus its issues, merge requests, pipelines and settings.
Ten projects, twelve engineers, and one contractor whose access should expire in March.
CI/CD means every push triggers an automatic sequence: build, test, deliver. Continuous Integration merges and tests code often.
A password committed to Git is a password everyone with repo access owns, forever, even after you delete it.
Your pipeline is queued. The status says "pending." Ten minutes later, still pending. Nothing is broken in your code. No runner wants your job.
It is a Friday evening at a Pune fintech.
A project is the basic unit in GitLab: one Git repository plus its issues, merge requests, pipelines and settings.
Ten projects, twelve engineers, and one contractor whose access should expire in March.
CI/CD means every push triggers an automatic sequence: build, test, deliver.
A password committed to Git is a password everyone with repo access owns, forever, even after you delete it.
Your pipeline is queued. The status says "pending." Ten minutes later, still pending. Nothing is broken in your code.
Tests passing is nice. Code running somewhere a user can reach it is the point.
You will build a tiny Node.js app and a three-stage pipeline: test, build image, deploy behind a manual gate.
Quick reference Common mistakes Forgetting that jobs are isolated is the classic.
Roles that use the skills in this module.
DevOps Engineer
₹8L - ₹18L a year
Cloud Engineer
₹6L - ₹14L a year
Site Reliability Engineer (SRE)
₹10L - ₹24L a year
Not a software engineer sheet. Every problem comes from real DevOps, SRE, Platform and Cloud interviews, from your first script to a system you build yourself.
Open the Coding Sheet