GitLab In One Shot | DevOps Production CICD Pipelines [Hindi]

Summary

The video is a hands-on introduction to GitLab, focused on setting up a project and building a CI/CD pipeline. The instructor compares GitLab with GitHub and Bitbucket, then demonstrates project organization, repository access, pipelines, runners, variables, secrets, artifacts, and deployment troubleshooting.

GitLab and Other Platforms

• GitLab provides Git repository hosting, project-management features, and CI/CD capabilities.
• The instructor highlights GitLab’s self-managed option, contrasting it with GitHub’s hosted service and paid enterprise offering.
• He characterizes GitHub as especially prominent in open-source collaboration and Bitbucket as closely integrated with Atlassian tools such as Jira. These are broad comparisons from the presentation, not detailed product evaluations.
• GitHub repositories can be brought into GitLab using an import option or by supplying a repository URL.

Organizing Projects and Setting Up Access

• Groups collect team members and their projects. Group membership can determine access to projects within the group.
• GitLab calls a repository a project; projects can be placed inside groups. The instructor contrasts this with GitHub’s usual user-or-organization and repository structure.
• Projects and groups can be public or private. Users can be invited with roles such as guest, reporter, developer, maintainer, or owner.
• The demo creates a GitLab account, a group, and projects, then imports a repository.
• For command-line access, the instructor demonstrates generating an SSH key pair and adding the public key to GitLab. He also notes that HTTPS access can use a personal access token.
• Once authenticated, familiar Git commands such as git clone, git push, and git pull work with GitLab.

Creating a CI/CD Pipeline

The key configuration file is .gitlab-ci.yml, which is placed in the project repository. GitLab uses it to define the pipeline.

• A pipeline is organized into stages, such as build, test, push, and deploy.
• Jobs belong to stages and specify scripts to run. For example, a build job might run a Docker build command, followed by test and image-push jobs.
• Jobs in the same stage can run in parallel—for example, separate development, staging, and production test jobs.
• Committing the CI configuration triggers the pipeline. GitLab’s interface shows pipeline status, individual jobs, logs, and results. The instructor also demonstrates the web IDE and pipeline editor.
• The instructor presents GitLab’s built-in CI/CD as a way to create pipelines without installing Jenkins for that project.

Variables, Secrets, and Artifacts

• GitLab provides predefined CI variables, such as variables identifying the project or commit.
• Users can define their own variables and reference them in job scripts.
• Sensitive values—such as Docker Hub credentials—should be stored as CI/CD variables rather than written directly into the pipeline file. The demo uses masked variables and discusses protecting variables for selected branches or environments.
• Artifacts preserve files produced by jobs, such as logs or test results. The pipeline configuration specifies which paths to save and how long to retain them. The video demonstrates downloading artifacts from a completed job and correcting a path-related mistake.

Shared and Self-Hosted Runners

A runner is the process or machine that picks up and executes GitLab CI jobs.

• GitLab offers shared or instance runners; the instructor says the account has access to hosted runners.
• Teams can also install a self-hosted runner on their own machine or server.
• The demonstration installs GitLab Runner on an Ubuntu-based cloud instance, registers it to the project, and chooses an executor. Runner tags can route particular jobs to the appropriate runner.
• A job may remain pending or become stuck if no eligible runner is online, the runner is disabled, or its tags or branch protections do not match.
• The tutorial also illustrates troubleshooting a runner that logs out between jobs and resolving a Docker permission issue by granting the runner user the required Docker access.

Docker Deployment Example and Troubleshooting

The instructor builds a sample pipeline for a Dockerized application, with build, test, image-push, and deployment steps. During the walkthrough, several problems arise, including invalid YAML, missing or incorrectly scoped variables, runner availability, Docker permissions, credentials, and a Docker Compose command issue.

The examples show how to inspect job logs, revise the configuration, and retry jobs. The main lesson is that pipelines often require iterative debugging; a successful configuration depends on correct YAML, runner setup, credentials, and available tools.

DevSecOps Takeaway

The closing section describes adding security checks to a delivery pipeline. In addition to building, testing, and deploying, teams can add code-quality analysis, image scanning, and application-security checks. The instructor presents this combination of development, operations, and security checks as the basis of DevSecOps.

Speakers and Sources Featured

• Shubham Londhe — instructor and presenter from TrainWithShubham.
• Madhu Pandey — credited with preparing GitLab notes for the community.
• Dheeraj Yadav — mentioned for Docker-related notes; the subtitles do not establish that he speaks in the video.
• Platforms and tools shown or discussed include GitLab, GitHub, Bitbucket, AWS, Docker, Docker Hub, GitLab Runner, Jenkins, SonarQube, Docker Scout, and OWASP.