Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Category Direction - Continuous Integration Scaling

Continuous Integration Scaling

In FY22, we have committed to SaaS First. In the Verify Stage, this means prioritizing the scale of Continuous Integration and ensuring our users on GitLab.com are leveraging a reliable and available service. We are focused on a goal of 20M builds per day as it represents not only a target to drive our future architecture, but a volume that we expect to achieve within several quarters.

Investment Allocation

Currently, we are staffing this Category with 10% of the Verify output, or equivalent to ~3 engineers in Verify. After we establish the load testing effort, we will evaluate if additional headcount will be required to support this effort.

We are expecting to on-ramp additional headcount in FY22-Q3 per product#2178, raising the percentage to ~24% of the Verify headcount.

Additional Resources

For specific information and features related to authoring/defining pipelines, check out Pipeline Authoring. You may also be looking for one of the following related product direction pages: GitLab Runner.

What's Next & Why

To begin working towards our goal, we will focus on building load testing environments in which we can perform measured tests around the initial primary architecture changes listed below:

  1. Define Scope of CI Scaling

Architectural Overview

Challenges

Vision Items

Our top vision items we have defined include:

  1. Improve GitLab CI/CD data model
  2. Improve Runner job queuing
  3. GitLab Runner Autoscaler architecture
Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license