CI/CD

Mon, 01 Jan 0001 00:00:00 +0000

GitLab CI/CD is a robust suite of DevOps tools embedded within GitLab, facilitating the automation of the entire software development lifecycle.

It integrates seamlessly with GitLab repositories, offering a complete pipeline framework to automate the processes of building, testing and deploying code.

Key Concepts and Components

Pipelines: Series of steps that execute in a defined order. Each step performs a specific actions, such as building the code, running tests, or deploying to an environment.
Pipelines could be triggered by various events, such as pushes to the repository, merge requests, or scheduled intervals. You can find a detailed explanation of pipelines .

Runners

Mon, 01 Jan 0001 00:00:00 +0000

GitLab Runners are essential components of GitLab’s CI/CD system. While your project’s pipeline defines what should be done (build, test, deploy steps), runners are the agents responsible for where and how those jobs are actually executed.

They enable teams to automate processes, enforce consistent environments, and scale their software delivery.

Runners execute your CI/CD job from the following options:

Instance Runners: aka Shared runners Available to all projects in a GitLab instance. For some security reason they may not be available on all platforms . On TDP C2 ,they are provided as a free managed service for quick testing or prototyping.
Managed Dedicated Runners: a managed service that guarantees the best quality of life, freeing time for developpers to focus on their projects.
Self-managed Dedicated Runners: Deploy and manage your own project or group runners on your infrastructure.

Runner Architecture

Runners are installed processes (services or daemons) that interact with the GitLab server.

Build on Software Factory

CI/CD

Key Concepts and Components

Runners

Runner Architecture