The Project | About Us | Contribute | Donations | License
HOME My courses Completed
◄ Previous
◄

GitLab CI/CD

Next ►
►

Introduction

GitLab CI/CD is a powerful tool integrated into GitLab, a web-based DevOps lifecycle tool that provides a Git repository manager providing wiki, issue-tracking, and CI/CD pipeline features. GitLab CI/CD allows you to automate the build, test, and deployment stages of your software development lifecycle.

Key Concepts

  • Pipeline: A pipeline is a collection of jobs that are executed in stages. Pipelines are defined in a .gitlab-ci.yml file.
  • Job: A job is a task that is executed by the runner. Jobs are defined within stages.
  • Stage: Stages are used to group jobs. Jobs in the same stage run in parallel, while stages run sequentially.
  • Runner: A runner is an agent that runs the jobs defined in the pipeline.

Setting Up GitLab CI/CD

Step 1: Create a GitLab Project

  1. Sign in to GitLab: If you don't have an account, create one at GitLab.
  2. Create a New Project: Click on the "New Project" button and follow the prompts to create a new project.

Step 2: Configure the .gitlab-ci.yml File

The .gitlab-ci.yml file is where you define your CI/CD pipeline. This file should be placed in the root directory of your repository.

stages:
  - build
  - test
  - deploy

build_job:
  stage: build
  script:
    - echo "Compiling the code..."
    - echo "Code compiled successfully."

test_job:
  stage: test
  script:
    - echo "Running tests..."
    - echo "All tests passed."

deploy_job:
  stage: deploy
  script:
    - echo "Deploying application..."
    - echo "Application deployed successfully."

Step 3: Commit and Push the .gitlab-ci.yml File

Commit the .gitlab-ci.yml file to your repository and push it to GitLab. This will trigger the pipeline defined in the file.

git add .gitlab-ci.yml
git commit -m "Add GitLab CI/CD configuration"
git push origin main

Understanding GitLab CI/CD Pipelines

Pipeline Visualization

Once the pipeline is triggered, you can visualize it in the GitLab UI:

  1. Navigate to CI/CD > Pipelines: This will show you the list of pipelines.
  2. Click on a Pipeline: This will show you the stages and jobs within the pipeline.

Example Pipeline

Here's a more complex example of a .gitlab-ci.yml file:

stages:
  - build
  - test
  - deploy

variables:
  TEST_ENV: "test"

build_job:
  stage: build
  script:
    - echo "Building the application..."
    - ./build.sh

test_job:
  stage: test
  script:
    - echo "Running tests in $TEST_ENV environment..."
    - ./run_tests.sh

deploy_job:
  stage: deploy
  script:
    - echo "Deploying to production..."
    - ./deploy.sh
  only:
    - main

Explanation

  • Variables: The variables section allows you to define environment variables that can be used in your scripts.
  • Only: The only keyword specifies that the deploy_job should only run on the main branch.

Practical Exercise

Exercise: Setting Up a Basic GitLab CI/CD Pipeline

  1. Objective: Create a GitLab CI/CD pipeline that builds, tests, and deploys a simple application.
  2. Steps:
    • Create a new GitLab project.
    • Add a .gitlab-ci.yml file with the following content:
stages:
  - build
  - test
  - deploy

build_job:
  stage: build
  script:
    - echo "Building the application..."

test_job:
  stage: test
  script:
    - echo "Running tests..."

deploy_job:
  stage: deploy
  script:
    - echo "Deploying the application..."
  1. Commit and Push: Commit and push the .gitlab-ci.yml file to trigger the pipeline.
  2. Verify: Check the pipeline status in the GitLab UI.

Solution

stages:
  - build
  - test
  - deploy

build_job:
  stage: build
  script:
    - echo "Building the application..."

test_job:
  stage: test
  script:
    - echo "Running tests..."

deploy_job:
  stage: deploy
  script:
    - echo "Deploying the application..."

Common Mistakes and Tips

  • Syntax Errors: Ensure that your .gitlab-ci.yml file is correctly formatted. YAML is sensitive to indentation.
  • Runner Issues: Make sure you have a runner configured to pick up the jobs. You can use GitLab's shared runners or set up your own.
  • Environment Variables: Use environment variables to manage sensitive information and configuration settings.

Conclusion

In this section, we covered the basics of GitLab CI/CD, including setting up a project, configuring the .gitlab-ci.yml file, and understanding pipelines. We also provided a practical exercise to help you get hands-on experience with GitLab CI/CD. In the next section, we will explore another popular CI/CD tool, CircleCI.

◄ Previous
◄
Next ►
►
The Project | About Us | Contribute | Donations | License
© Copyright 2024. All rights reserved