GitLab for DevOps: Projects to CI/CD Pipelines

Learn GitLab from first push to production: projects, groups, CI/CD pipelines, variables, runners, and a Docker deploy with a manual approval gate.

Prerequisites
~1 hour
9 Topics
Hands-on Scenarios

What You'll Learn

Understanding What GitLab Is and Why Teams Use It

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.

Getting Started With GitLab Projects and Your First Push

A project is the basic unit in GitLab: one Git repository plus its issues, merge requests, pipelines and settings.

Managing Groups, Members, and Permissions

Ten projects, twelve engineers, and one contractor whose access should expire in March.

Building Your First CI/CD Pipeline

CI/CD means every push triggers an automatic sequence: build, test, deliver. Continuous Integration merges and tests code often.

Using Variables, Secrets, and Artifacts

A password committed to Git is a password everyone with repo access owns, forever, even after you delete it.

Choosing Between SaaS Runners and Self-Hosted Runners

Your pipeline is queued. The status says "pending." Ten minutes later, still pending. Nothing is broken in your code. No runner wants your job.

Skills You'll Master

GITLABCI-CDGITLAB-RUNNERPIPELINESDEVOPS

Curriculum Index9 topics

Career Impact

Roles that use the skills in this module.

  • DevOps Engineer

    ₹8L - ₹18L a year

    High Demand
  • Cloud Engineer

    ₹6L - ₹14L a year

    Very High
  • Site Reliability Engineer (SRE)

    ₹10L - ₹24L a year

    Critical / Niche
See how this is asked in interviews

Practice on the Coding Sheet

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