|Estimated Date Ended||2023-07-05|
|Slack||(only accessible from within the company)|
|Google Doc||CI Build Speed Working Group Agenda (only accessible from within the company)|
We aim to create a working group to establish a repeatable process and framework to measure CI build speed and performance (time-to-result). The objective is to communicate to the market and customers a GitLab point of view, position GitLab CI build performance as the market leader, and provide guidance to customers on optimization considerations so that they can maximize developer efficiency while balancing compute costs for CI builds.
CI build speed and performance (time-to-result) and CI build cost efficiency are essential competitive vectors especially given the improved maturity of the CI/CD solutions in the market. The brand Q4 FY23 qualitative research study data indicates that "GitLab leads the pack in associations with speed." However, our internal benchmark testing, (slides, report, of CI build performance on GitLab SaaS had mixed results. Therefore GitLab SaaS customers' perception of CI build performance could be different than self-managed customers or even GitLab SaaS customers that choose to manage their own CI build environment.
Additionally, to date, competitors, (Github, Harness.io), have generally focused on build time duration when discussing CI build speed and performance. While build time duration is the default performance measure, the working group must evaluate if there are other discrete measurements to include in the framework.
|Working Group Role||Person|
|Executive sponsor||Mike Flouton @mflouton|
|Facilitator||Darren Eastman @DarrenEastman|