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.
In FY23 a top priority for us is 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.
For specific information and features related to authoring/defining pipelines, check out Pipeline Authoring. For specific information and features related to running and managing pipelines check out Continuous Integration. You may also be looking for one of the following related product direction pages: GitLab Runner.
Now that we have delivered the Next CI/CD scale target: 20M builds per day by 2024 blueprint and related scope on queueing mechanisms via gitlab&5909, primary key capacity via gitlab#325618, and handling large amounts of data via gitlab&6009, and have delivered our CI/CD Time Decay blueprint, we are ready to begin Phase II of CI Scaling: partitioning data with the CI/CD Time Decay pattern.
As the new queuing mechanism rolls out, performance changes will be visible in the Duration of the builds queue retrieval using the big query SQL
Our top vision items we have defined include:
For the next phase of this category, we will be working across Database and Verify to instrument a cross functional product group. The DRIs are:
The following epics are used to coordinate the phases of CI Partitioning:
For internal questions, reach out to the slack channel #f_ci_time_decay and tag