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 Executors

Shell Executor

< >

4.4. Shell Executor

shell-logo.png

Description: Runs jobs using the host’s shell.

Best For: Simple tasks, no additional dependencies.

Why? The Shell executor offers simplicity and ease of setup, making it suitable for straightforward tasks without complex dependencies. It does not require additional setup or containerization, making it a lightweight option for quick jobs. However, it lacks the isolation provided by Docker or Kubernetes executors, which may be a concern for security-sensitive workflows.

Advantages

  • Simplicity: Easy to set up and use for simple tasks.
  • No Additional Dependencies: Suitable for tasks with minimal dependencies.

Disadvantages

  • Lack of Isolation: The Shell executor does not provide the same level of isolation as Docker or Kubernetes, potentially compromising security.
  • Environment Variability: Reliance on the host environment may lead to inconsistencies across different environments, resulting in potential issues during execution.