🌟Day 27: Learn How to Use GitLab

Hey everyone! 👋 On my 27th day of the 90 Days of DevOps challenge, I dove into installing GitLab. Whether you're new to coding or looking to expand your skills, this guide will walk you through the basics of GitLab in a simple way. Let’s dive in! 🎉

📌 What is GitLab?

GitLab is like a Swiss Army knife for developers. It’s an all-in-one platform that helps you manage your code, collaborate with others, and automate your workflows. Think of it as your go-to tool for all things DevOps! 🛠️

🌟 Features of GitLab

1. Version Control with Git

GitLab uses Git to track changes in your code. This means you can see who made what changes and work with others without any confusion. 📚

2. Repository Management

Create your own code repositories on GitLab. Repositories are like folders where you store your project files. You can make them private (only you can see) or public (everyone can see). 🔒

3. CI/CD Pipelines

Automate your coding tasks with CI/CD pipelines. CI (Continuous Integration) checks your code for errors, and CD (Continuous Deployment) automatically sends your updates to users. 🚀

4. GitLab Runners

These are mini-robots that run your CI/CD jobs. They help automate tasks, so you don’t have to do everything manually. 🤖

5. Issue Tracking and Project Management

Keep track of tasks, bugs, and project progress all in one place. It’s like having a built-in to-do list for your projects. 📝

6. Security and Compliance

GitLab helps you keep your code secure and compliant with industry standards. It scans your code for vulnerabilities and ensures everything is up to par. 🛡️

🔍 How to Get Started with GitLab

1. Create a GitLab Account

Go to GitLab and sign up for a free account. Once you’re in, you can start creating projects right away! 🌟

2. Create a New Project

Click on the “New Project” button.
Choose to create a blank project, import an existing one, or use a template.
Fill in the project name and description.
Choose the visibility level (private, internal, or public).
Click “Create project”.

And voila! You’ve just created your first GitLab project! 🎉

3. Clone Your Repository

To work on your project locally, clone the repository to your computer. Open your terminal (command prompt) and type:

git clone https://gitlab.com/username/your-project.git

Replace username and your-project with your GitLab username and project name.

4. Make Changes and Push to GitLab

Navigate to your project directory:
```
 cd your-project
```
Make some changes to your code.
Stage the changes:
```
 git add .
```
Commit the changes:
```
 git commit -m "Your commit message"
```
Push the changes to GitLab:
```
 git push origin main
```

🚀 Setting Up CI/CD Pipelines

CI/CD pipelines help automate your workflow. Here’s how to set one up:

1. Create a .gitlab-ci.yml File

In the root of your project, create a file named .gitlab-ci.yml. This file tells GitLab how to run your pipeline.

stages:
  - build
  - test
  - deploy

build:
  stage: build
  script:
    - echo "Building the project..."
    - # Add your build commands here

test:
  stage: test
  script:
    - echo "Running tests..."
    - # Add your test commands here

deploy:
  stage: deploy
  script:
    - echo "Deploying the project..."
    - # Add your deploy commands here

2. Commit and Push the .gitlab-ci.yml File

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

GitLab will automatically start running your pipeline. You can check its progress in the CI/CD > Pipelines section of your project.

🤖 Setting Up GitLab Runners

GitLab Runners execute your CI/CD jobs. Here’s how to set one up:

1. Install GitLab Runner

Follow the installation instructions from the official GitLab Runner documentation.

2. Register the Runner

Run the following command:
```
 gitlab-runner register
```
Enter your GitLab URL (e.g., https://gitlab.com).
Enter the registration token from your project (found in Settings > CI/CD > Runners).
Give your runner a name (e.g., My Runner).
Enter tags for the runner (e.g., my-runner).
Choose the executor (e.g., shell).

3. Verify the Runner

Your runner should now appear in your project’s Settings > CI/CD > Runners section. You’re all set to automate your tasks! 🎉

🛡️ Keeping Your Code Secure

GitLab helps keep your code secure with tools like SAST (Static Application Security Testing) and DAST (Dynamic Application Security Testing).

1. Enable SAST

Add this to your .gitlab-ci.yml file:

include:
  - template: Security/SAST.gitlab-ci.yml

2. Enable DAST

Add this to your .gitlab-ci.yml file:

include:
  - template: Security/DAST.gitlab-ci.yml

GitLab will automatically run these security scans as part of your pipeline, checking for vulnerabilities. 🛡️

🎯 Conclusion

GitLab is a fantastic tool that simplifies the development and deployment of your projects. By using its features like version control, CI/CD pipelines, runners, and security tools, you can improve your workflow and ensure high-quality software.

If you have any questions or want to share your experiences, feel free to leave a comment or reach out to me. Let’s learn and grow together! 🌱

Happy Learning! 😊