GitLab CI/CD
A comprehensive continuous integration and continuous delivery platform built directly into GitLab, enabling concurrent automated testing and secure software deployments.
About GitLab CI/CD
GitLab CI/CD is an integral component of the broader GitLab DevSecOps platform, designed to offer continuous integration, continuous delivery, and continuous deployment within a single unified application. Rather than stitching together various third-party tools, engineering teams can manage source code, execute complex build pipelines, and monitor deployments in one interface, significantly reducing the "toolchain tax."
Pipelines are configured using a straightforward .gitlab-ci.yml file placed at the root of the repository. The platform relies on GitLab Runners—agents that execute the jobs—which can be hosted by GitLab (SaaS) or self-managed on a team's own infrastructure. This architecture ensures high scalability, as organizations can effortlessly provision autoscaling runner fleets to handle massive concurrent build volumes without bottlenecking.
Security and compliance are core tenets of the platform. GitLab CI/CD embeds security scanning directly into the pipeline, including Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and container scanning. This shift-left approach ensures vulnerabilities are identified and remediated before code ever reaches a production environment.
Key Features
- Built-in DevSecOps: Integrated security testing (SAST, DAST, dependency scanning) directly into the pipeline execution flow.
- Auto DevOps: Automatically build, test, configure, and deploy applications using predefined, best-practice CI/CD templates.
- Environment Management: Track deployments across staging and production environments, complete with deployment history and roll-back capabilities.
- GitLab Runners: Flexible agent architecture supporting Docker, Kubernetes, Linux, Windows, and macOS for scalable job execution.
- Review Apps: Automatically spin up dynamic environments for every merge request, allowing stakeholders to preview changes live before merging.
- Directed Acyclic Graph (DAG): Configure complex pipeline relationships to execute jobs out of order as soon as their specific dependencies are met.
Pricing
Pricing Model: Freemium, Per User Subscription, Custom Enterprise Pricing
1. Free
Price: $0 per user/month
Features:
- Built-in source code management and CI/CD
- 400 compute minutes per month on GitLab.com
- 5 users per private top-level group
- 10 GiB adjustable storage
- Static Application Security Testing
- Support for self-managed runners
2. Premium
Price: $29 per user/month
Billing: Annually
Features:
- Everything included in Free
- Advanced CI/CD capabilities
- 10,000 compute minutes per month on GitLab.com
- Unlimited licensed users
- Team project management
- SLA management
- Priority support
- 12 GitLab Credits per user/month included as a limited-time promotional offer
3. Ultimate
Price: Custom Pricing
Billing: Contact Sales
Features:
- Everything included in Premium
- 50,000 compute minutes per month on GitLab.com
- Advanced application security testing
- Software supply chain security
- Vulnerability management
- Compliance and governance
- Strategic portfolio management
- Value stream management
- Unlimited guest users
- 24 GitLab Credits per user/month included as a limited-time promotional offer
4. Additional Compute Minutes
Price: $10 per 1,000 compute minutes
Billing: One-time purchase
Availability: All GitLab plans
Additional compute minutes can be purchased for CI/CD pipelines exceeding their included GitLab.com runner allocation.
Pricing last updated: October 30, 2026 at 12:00 AM
Use Cases
- Embedding rigorous security compliance and vulnerability scanning into every developer merge request.
- Spinning up ephemeral, containerized review environments for QA teams to validate front-end changes visually.
- Managing complex monorepo pipelines using DAG-based execution and parent-child pipeline configurations.
- Hosting highly concurrent self-managed runner fleets on Kubernetes to eliminate cloud compute costs for CI.
Pros & Cons
Pros:
- A single application for source control, CI/CD, and security monitoring drastically reduces administrative overhead.
- Self-managed runners provide completely unlimited CI/CD compute minutes.
- Excellent built-in environment tracking and robust deployment rollback features.
Cons:
- The SaaS free tier allowance of 400 compute minutes is highly restrictive for active development teams.
- Premium and Ultimate pricing tiers can become expensive for organizations with large user bases.
Integrations
Kubernetes, AWS, Google Cloud, Microsoft Azure, Jira, Slack, Prometheus, HashiCorp Vault
FAQ
What is the difference between GitLab SaaS and GitLab Self-Managed?
GitLab SaaS is hosted by GitLab, where you pay per user and utilize their shared runners (with a specific minute allowance). GitLab Self-Managed means you install the software on your own servers, giving you complete control over data and unlimited CI compute minutes using your own runners.
What is a GitLab Runner?
A GitLab Runner is an open-source application that works with GitLab CI/CD to run pipeline jobs. They can be installed on physical machines, virtual machines, or in containers (like Docker or Kubernetes) and can be self-hosted or managed by GitLab.
How does Auto DevOps work?
Auto DevOps provides a pre-configured CI/CD pipeline that automatically builds, tests, secures, and deploys applications based on the language and framework detected in the repository, requiring zero manual YAML configuration.
Does GitLab CI/CD support macOS for iOS development?
Yes, GitLab SaaS provides macOS shared runners for building and testing Apple ecosystem applications. Alternatively, teams can host their own macOS runners by installing the agent on Apple hardware.
What are Review Apps?
Review Apps automatically deploy a live instance of your application for a specific branch or merge request. This provides a URL where developers, designers, and QA can preview the changes in a production-like environment before merging the code.
Last edited
October 29, 2026 at 7:18 PM by Venkatraman Chandrasekaran
