Back to Tools
CI/CD
GitLab CI
GitLab CI provides repository-integrated automation using a YAML-based pipeline model. It supports build, test, security scanning, and deployment workflows directly inside the GitLab platform.
CI/CDGitLabPipelines
Key Concepts
Pipelines are defined in .gitlab-ci.yml.
Stages organize job execution order.
Runners execute jobs on available infrastructure.
Built-in DevSecOps capabilities are a strong advantage.
Common Interview Questions
What is GitLab CI?
How do stages work in GitLab CI?
What is a GitLab runner?
Use Case
Use GitLab CI when your code, pipelines, and DevOps workflows are centered in GitLab.
Common Use Cases
Running build and deployment pipelines in GitLab-centric teams.
Combining SCM, CI/CD, and security workflows in one platform.
Managing internal DevSecOps pipelines.
Pros
Strong all-in-one platform experience.
Good security and DevSecOps integrations.
Clean YAML-based configuration model.
Cons
Can be heavier if you do not use the rest of GitLab ecosystem.
Self-managed GitLab requires meaningful operational effort.
Runner management becomes important at scale.