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.
| Stage | Verify |
| Maturity | Complete |
| Content Last Reviewed | 2024-01-23 |
Thanks for visiting this category direction page on Continuous Integration (CI) in GitLab. This page belongs to the Verify Stage and is maintained by Rutvik Shah (E-Mail).
This direction page is a work in progress, and everyone can contribute:
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 the leading DevOps tool on the market, as well as a leader in Forrester's most recent and final 2019 Q3 Cloud Native CI Wave, and it's important for us that we continue to innovate in this area and provide not just a "good enough" solution, but a speedy and reliable one.
Making it easy to run a pipeline is our first focus and this applies to both running a pipeline manually as well as triggering one automatically when submitting a code commit or a merge request. In addition, we want to provide data for examining your pipeline's performance, so that you can optimize CI configurations to make your pipelines run more efficiently.
For specific information and features related to authoring and pipelines, check out Pipeline Authoring. For work related to Pipeline Abuse Prevention, see the Category page.
You may also be looking for one of the following related product direction pages: Overall Vision of the Verify stage and GitLab Runner.
Our strategy to regain a category maturity of "Lovable" is two-fold - first, a renewed focus on strengthening the core features of CI that support running a pipeline; and second, deliver features that provides more users with the ability to run pipelines in a project.
In CY24, our plan is to empower CI users to do more with GitLab pipelines. This includes:
Support GitLab-GCP Continuous Integration by helping deliver the Frontend for the Runner set-up pieces with the GCP console
We are currently focusing on delivering the capability to always run after_script for canceled jobs and adding canceling state for jobs.
The Pipeline Execution Group is an efficient team releasing almost 66 MRs a milestone. Some of the top deliverables over the last quarter are:
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.
The majority of CI market conversation is between us, Jenkins, and GitHub Actions at this point. An example of this placement is from Jet Brain's 5th annual Developer Ecosystem Survey which has placed GitLab as #2 CI solution for enterprises. Atlassian has built BitBucket Pipelines, a more modernized version of Bamboo, which is still in the early stages. Microsoft is maintaining (at least for now) Azure DevOps at the same time as GitHub Actions but for personal usage GitHub Actions is gaining traction among developers. CodeFresh and CircleCI have both released container-based plugin model, similar to GitHub Actions. CircleCI in particular is known for very fast startup times and we're looking to ensure we keep up or get even faster. Jenkins is largely seen as a legacy tool, and most people we speak with are interested in moving off to something more modern. We are addressing this with our Jenkins Importer category which is designed to make this as easy as possible.
From GitHub's 2023 Roadmap, we are seeing GitLab-reminiscent features which include Pull Request Merge Queue, akin to Merge Trains with a fit-finish that we aim to make easier in gitlab#294169. Also to note is an emphasis on governance and controls with Audit Log streaming, bringing parity to the capabilities GitLab has created with the Compliance group's Audit Event streaming.
For Continuous Integration, our "What's Next & Why" are targeting the following personas, as ranked by priority for support:
Our current maturity is at "Complete" and the next maturity target is "Lovable" (see our definitions of maturity levels). In order to maintain our lead while staying ahead of the changing DevSecOps landscape needs for stability, performance and quality we need to reestablish a strong foundation of the core elements for CI. As such, we are prioritizing bugs and user experience improvements, while continuing to design and validate features for future implementation that move our vision forward. The following investments will be key to moving our maturity forward in the next two quarters:
There are a few key findings from the Forrester Research analysts on our CI solution. GitLab is seen as capable as the solutions provided by the hyperclouds themselves, and well ahead of other neutral solutions. This can give our users flexibility when it comes to which cloud provider(s) they want to use. We are also seen as the best end to end leader, with other products not keeping up and not providing as comprehensive solutions. What this tells us is that it is important for us to continue to innovate and make it hard or even impossible for competitors to maintain pace. As such, our path to improving our analyst performance matches our solutions above in terms of staying ahead of our competitors.