Category Direction - Continuous Integration

The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.

Continuous Integration

Continuous Integration


Stage	Verify
Maturity	Competitive
Content Last Reviewed	`2025-06-17`
Maintained By	Rutvik Shah ([email protected])

Overview

Continuous Integration is an important part of any software development cycle. We recognize a key advantage of GitLab CI is that we can define pipelines as code, while making CI easy to use, reliable, and accurate in terms of its results. We are very proud that we are recognized as a leader in DevOps Platforms in the Gartner Magic Quadrant, as well as a leader in Forrester's Wave: DevOps Platform.

For specific information and features related to authoring pipelines, check out Pipeline Authoring.

You may also be looking for one of the following related product direction pages: Overall Vision of the Verify stage and GitLab Runner.

Strategy and Themes

Our strategy focuses on delivering advanced CI/CD capabilities while providing enterprise-grade solutions that scale with your organizations needs. We believe in making automation accessible to all teams, then delivering advanced capabilities that promote greater efficiency and governance without compromising on security as your DevSecOps maturity grows.

1 year plan

For FY26 (ending February 2026):

We will be maintaining our Continuous Integration functionality with a focused approach:

Bug Resolution: Prioritizing critical S1/S2 issues that have exceeded their service level objectives
Community Collaboration: Actively supporting community contributions that enhance this category.
Feature Development: We will focus on delivering the following capabilities
- Filter by job name on job list view
- Improve parent/child pipeline experience with the ability to show security reports from a child pipelines in Merge Request Widget

What is next for us

Roll out the filter by job name on job list view with the ability to search in the past 3 months as an experiment
Critical S1/S2 issues that have exceeded their service level objectives

What we are currently working on

We are currently focusing on

Critical S1/S2 issues that have exceeded their service level objectives
A feature to notify project owners/maintainers when a scheduled pipeline no longer has an owner

What we recently completed

The top deliverables from the Pipeline Execution group over the last quarter are:

Use Claude Sonnet 4.0 for Root Cause Analysis
Made Root Cause Analysis available for Premium customers

What is Not Planned Right Now

CI related notifications (by email or via integration with other tools)
CI related API endpoints (unless related to features on the roadmap)
CI related permissions (non-bug issues)
Configure CI/CD Quotas by project going forward we will work with the community to review and merge contributions but are not planning active development on new features.

Best in Class Landscape

BIC (Best In Class) is an indicator of forecasted near-term market performance based on a combination of factors, including analyst views, market news, and feedback from the sales and product teams. It is critical that we understand where GitLab appears in the BIC landscape.

Key Capabilities

Target Audience

For Continuous Integration, our "What's Next & Why" are targeting the following personas, as ranked by priority for support: