GitLab CI CD Pipeline Udemy Course

In this article we are going to cover GitLab CI CD Pipeline Udemy Course | GitLab CI CD Pipeline Hands On for DevOps | GitLab CI CD Pipeline Hands On for DevOps Engineer | GitLab CI/CD Pipeline Tutorial | End to End CI/CD Pipeline GitLab


  • GitLab Account
  • Payment Verified with Credit Card which is free of charge
  • Basics of YAML, Linux Commands

What is GitLab CI CD?

GitLab CI/CD (Continuous Integration/Continuous Deployment) is a powerful DevOps tool provided by GitLab, a web-based platform for version control, source code management, and CI/CD. It allows you to automate various stages of software development, from building and testing to deploying and monitoring your applications. Here’s an overview of GitLab CI/CD:

  1. Version Control: GitLab provides a built-in version control system, which is usually Git. Developers use Git to manage their source code and collaborate on projects.
  2. GitLab CI/CD Configuration: You define your CI/CD process by creating a .gitlab-ci.yml file in the root of your GitLab repository. This file contains configuration instructions for your CI/CD pipelines.
  3. CI/CD Pipelines: GitLab CI/CD pipelines are a series of automated steps that run whenever changes are pushed to your repository. These pipelines can include the following stages:
  • Build: Compiling and building your application.
  • Test: Running tests to ensure code quality and reliability.
  • Deploy: Deploying your application to a specific environment, such as staging or production.
  • Monitoring: Setting up monitoring and alerting to track the performance of your deployed application.
  1. Runners: GitLab Runners are agents that execute the jobs defined in your .gitlab-ci.yml file. You can use shared runners provided by GitLab, or you can set up your own runners for more control.
  2. Artifacts: You can define what files should be saved as artifacts after each job. These artifacts can be used in subsequent jobs or downloaded as build outputs.
  3. Environments: GitLab allows you to define environments for your application, such as “staging” or “production.” Each environment can be associated with a specific branch, and you can trigger deployments to these environments automatically.
  4. Manual Approvals: You can configure jobs to require manual approval before they proceed to the next stage. This is useful for ensuring certain actions are validated before deploying to production.
  5. Integration: GitLab CI/CD can be integrated with various tools and services, such as Docker, Kubernetes, and more, to simplify the deployment and management of your applications.
  6. Container Registry: GitLab provides a built-in container registry where you can store Docker images, making it easy to manage and deploy containerized applications.
  7. Monitoring and Security: GitLab also offers built-in monitoring and security features, allowing you to track the performance and security of your applications throughout the CI/CD process.

To get started with GitLab CI/CD, you would typically:

  1. Create a .gitlab-ci.yml file in your repository to define your CI/CD pipeline.
  2. Configure GitLab Runners to execute the pipeline.
  3. Commit code changes and push them to your repository.
  4. GitLab will automatically trigger CI/CD pipelines based on your .gitlab-ci.yml configuration.

This approach streamlines development, testing, and deployment, leading to faster and more reliable software delivery.

Get 44% OFF on GitLab CI/CD Pipeline Tutorial Udemy Course

GitLab Basics Tutorial

  • What is GitLab | Features of GitLab | GitLab Architecture | What GitLab CI/CD Pipeline
  • How to create a new project in GitLab
  • How To Create and Add SSH Key to GitLab
  • Create Group and Users in GitLab
  • Jobs in GitLab CI | Stages in GitLab CI Explained
  • GitLab CI Artifacts Example | How to use artifact in GitLab CI

GitLab Runner Tutorial | Install and Register GitLab Runner

  • Install GitLab Runner on Ubuntu 22.04 LTS
  • Install GitLab Runner on Redhat Linux
  • Install GitLab Runner on Windows

YAML Basis Tutorial with Example

  • What is YAML, YAML Data types, YAML Indentation

Continuous Integration (CI) with GitLab | GitLab CI

  • Run your first GitLab CI CD pipeline [2 Steps]
  • GitLab CI/CD Environment Variables | GitLab Predefined Variables
  • Build Java Project using Maven in GitLab CI
  • How to Build Java Project using Gradle in GitLab CI | GitLab CI Java Gradle

JUnit Test with GitLab CI | Junit with GitLab CI Examples

  • Generate JUnit Reports for Java Maven Project using GitLab CI

Java Code Coverage(JaCoCo) with GitLab CI

  • Java Code Coverage(JaCoCo) with GitLab CI

SonarQube Integration with GitLab CI

  • Integrate SonarQube with Java Maven project using GitLab CI
  • SonarQube Integration for Java Gradle Project using GitLab CI
  • SonarQube Integration for Node JS Project using GitLab
  • Sonarqube Integration for Python Project using GitLab CI

Build Docker Image using GitLab CI

  • How to Push a Dockerized Node.js App to GitLab Container Registry
  • How to Build and Push Docker Image to AWS ECR | GitLab CI CD Docker AWS
  • How to Build Docker Image and Push to DockerHub using GitLab CI

Contineous Deployments (CD) with GitLab

  • Upload file to AWS S3 Bucket using GitLab CI/CD | Upload file to AWS S3
  • Deploy war file in Tomcat using GitLab CI Pipeline
  • How to Deploy jar file in tomcat using GitLab CI Pipeline
  • Integrating  AWS EKS with GitLab | Connect AWS Kubernetes Cluster with GitLab
  • Deploy Node JS App on AWS EKS using GitLab CI CD | Deploy to EKS using GitLab
  • Deploy Node JS Helm Chart on AWS EKS using GitLab CI CD
  • Deploy Java Helm Chart on EKS using GitLab CI CD

Who this course is for:

  • Software Developers and Testers who is learning to build pipeline using GitLab
  • DevOps Engineer, SRE, IT Admin, IT Professionals

Get 44% OFF on GitLab CI/CD Pipeline Tutorial Udemy Cours

Related Udemy Course:

GitHub Actions Udemy Course for DevOps

About SkyHigh Services

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Share via
Copy link