Logo
Intro
CI/CD Fundamentals
Introduction to CI/CD Pipelines
Benefits of Using GitLab CI/CD
GitLab CI/CD Components
Practical Implementation of CI/CD Pipelines
.gitlab-ci.yml Basics
How to Create a .gitlab-ci.yml File
Basic Structure of a .gitlab-ci.yml File
Step by Step Guide to Creating a .gitlab-ci.yml File
Advanced Configuration
Full Example
GitLab Runners
GitLab Runners
Choosing the Right Runners
Runner Configuration
Runner Management Best Practices
Why Use Runners?
GitLab Executors
What Are GitLab Executors?
Why Are Executors Important?
Docker Executor
Shell Executor
Specific Runners
Installing Specific Runners
Installing GitLab Runner on Linux
Installing GitLab Runner on macOS
Installing GitLab Runner on Windows
Creating the Runner
Registering the Runner
Verifying the Runner
Configuring the Runner
Artifacts
Artifacts in GitLab CI/CD
Storing Artifacts in .gitlab-ci.yml
Retrieving Artifacts
Using Artifacts in Subsequent Jobs
Advanced Artifact Management
Conclusions
Documentation Generation
Documentation Generation in GitLab CI/CD Pipelines
Setting Up MkDocs
Configuring MkDocs
Creating Documentation Pages
Summary
Monitoring
Basic Monitoring in GitLab CI/CD
Enable Pipeline Monitoring
Add Notifications for Pipeline Events
Add Notifications for Pipeline Events

GitLab Runners

Why Use Runners?

< >

3.5. Why Use Runners?

  • Resource Isolation:

Runners isolate jobs from each other, preventing interference and ensuring consistent job execution environments.

  • Efficiency:

By distributing workload across multiple runners, teams can parallelize job execution, reduce build times, and improve overall pipeline efficiency.

  • Flexibility:

Runners support various execution environments (e.g., Docker, Kubernetes), enabling teams to use different tools, libraries, and dependencies without affecting other projects.